delete_milestone

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

The description simply says 'delete', which aligns with the destructiveHint annotation but adds no new behavioral insights. It does not disclose idempotency behavior, side effects, or error conditions, leaving the annotations to carry the full burden.

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 sentence with no extraneous information, making it concise. However, it is arguably too brief for a destructive operation with idempotency, missing context like irreversibility.

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 destructive and idempotent nature of the tool, the description lacks crucial context such as what happens if the milestone does not exist, whether the operation is reversible, or any required permissions. While the schema covers parameters, the description does not address behavioral or error scenarios, making it incomplete.

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 already provides descriptions for both parameters (code and id), achieving 100% coverage. The description adds no additional meaning beyond what the schema already conveys, 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 resource (milestone), distinguishing it from sibling tools like create_milestone or update_milestone. However, it lacks any additional context or constraints.

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, no prerequisites, and no conditions under which it should not be used. It only states the basic action.

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