delete_project

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

No annotations exist, so the description must bear the full burden. It only states 'delete,' implying a destructive action, but fails to disclose irreversibility, permission requirements, side effects, or what happens to associated data. This is insufficient for an agent.

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 with a single sentence. While it avoids verbosity, it sacrifices necessary detail. However, for a simple tool, brevity is not a flaw per se, but it could benefit from more context without being overly long.

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 destructive operation with no output schema and minimal description, the tool provides insufficient context. It fails to explain return values, error handling, or confirmation—critical for an agent executing deletions. The description is incomplete given the tool's sensitivity.

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 only parameter 'project' is a string with no description in the schema (0% coverage). The tool description adds no semantic meaning beyond the schema, leaving the agent uncertain about format, expected values, or how to specify the project.

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 'Delete a project from the index' clearly states the action (delete), the resource (project), and the context (from the index). This distinguishes it from sibling tools like list_projects or manage_adr, which are the only potentially overlapping tools.

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 usage guidelines are provided. The description does not specify when to use this tool over alternatives, nor does it mention prerequisites, conditions, or when not to use it. The agent has no guidance on decision-making.

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