dev_delete_project

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description merely states the operation without disclosing behavioral implications like irreversibility, cascading deletions, or authorization requirements. Since no annotations are provided, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise (one sentence). While efficient, it sacrifices necessary detail for a tool with no annotations and a bare schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one parameter, the description is incomplete. It lacks essential context about the parameter, return values, side effects, and usage context.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'projectId' is not explained at all. The description adds no meaning beyond the schema's type definition. With 0% schema coverage, this is critically inadequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states the action ('Delete') and resource ('Lamatic project'), making the purpose clear. However, it does not differentiate from other delete tools for different resources or provide any additional context about what 'delete' entails.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like dev_create_project or dev_update_project. The description lacks any contextual hints about prerequisites or typical scenarios.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.