delete_project

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It discloses the destructive nature (deleting all test cases) but omits critical details: whether deletion is permanent, that the confirm parameter must be true, and whether the project itself is affected. This is insufficient for a mutation tool.

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 a single concise sentence with no redundant words. It efficiently conveys the core operation while leaving schema details to the schema. This is an ideal size for this simple tool.

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 two-parameter tool with no output schema, the description covers the core action but misses important contextual nuance: it does not mention permanence, the confirm requirement (only in schema), or the boundary that only test cases are deleted, not the project. The description is minimal but adequate, though more behavioral context would improve completeness.

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 input schema covers both parameters with clear descriptions (project name, confirm boolean). The description adds no additional semantic meaning beyond what the schema already provides. With 100% schema coverage, a baseline score of 3 is appropriate.

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 clearly states the specific action: deleting all test cases for a project. It distinguishes from sibling tools like add_test_case and list_test_cases by specifying the deletion scope. The tool name 'delete_project' could be ambiguous, but the description resolves this by clarifying it deletes test cases, not the project itself.

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?

The description implies when to use the tool: when you want to remove all test cases for a given project. It does not explicitly mention alternatives or exclusions, but the context is clear and it does not conflict with sibling tools. However, it lacks explicit guidance on prerequisites like project existence or confirmation behavior.

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