delete_defect

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

The description merely restates the action indicated by the name and annotations. It adds no detail about side effects, such as whether the deletion is permanent or cascades to related data. The annotations already provide 'destructiveHint=true', but the description fails to elaborate.

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—a single sentence with no fluff. It is front-loaded with the action and resource, though it could benefit from slightly more context. Still, it is efficient and to the point.

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?

Given the tool's simplicity (two required parameters, no output schema) and the detailed schema annotations, the description is minimally adequate. It explains the basic operation but lacks additional context like permanence or impact. More completeness would be helpful for a destructive tool.

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 descriptions and constraints (100% coverage). The description does not add any additional meaning beyond the schema, so 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 action ('Delete') and the resource ('a defect from a project'), effectively distinguishing it from sibling tools like 'resolve_defect' or 'create_defect'. It is specific and directly conveys the tool's purpose.

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 is provided on when to use this tool versus alternatives, such as 'resolve_defect' or 'update_defect_status'. The description does not mention prerequisites, consequences, or conditions for safe usage, which is important for a destructive action.

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