delete_milestone

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

The description explicitly states the action is irreversible ('This action cannot be undone'), which is valuable behavioral context beyond the basic purpose. However, with no annotations, it fails to disclose other important behaviors like permissions needed, impact on related objects, or return value.

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 very concise with two short sentences, no repetition, and all information is relevant. It is appropriate for a simple delete 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 single-parameter delete tool without output schema, the description covers the action and irreversibility but omits important context like authentication requirements, impact on associated data, and expected return value.

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?

Schema coverage is 100%, so the schema already documents the only parameter (milestone_id). The description does not add any additional semantic meaning beyond what the schema provides.

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 verb 'delete' and the resource 'milestone', and emphasizes permanence. It distinguishes from sibling delete tools targeting different resources (e.g., delete_epic, delete_issue).

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 provides no guidance on when to use this tool versus alternatives like update_milestone or other delete operations. It lacks context about prerequisites or conditions for deletion.

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