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

The description reveals that milestones are hard-deleted and not user-facing records, which goes beyond the destructiveHint annotation by explaining the consequence. It also states the expected return (confirmation of deletion), adding useful behavioral context that the structured annotations do not provide.

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 short and front-loaded, with the core action in the first sentence. The Args and Returns sections are standard and minimal, containing no filler or redundant content. Every sentence serves a purpose.

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 simple one-parameter delete operation with destructiveHint and idempotentHint annotations provided, the description covers the action, parameter, and return value. It does not address error cases or prerequisites, but these are not critical for a straightforward deletion 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 schema provides only the parameter name and type with no description (0% coverage), so the description's clarification that milestone_id is 'the milestone ID to delete' is essential and directly compensates. It fully explains the single parameter's meaning and role.

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 states 'Delete a milestone' with a specific verb and resource, and the parenthetical clarifies hard-deletion, which distinguishes it from update_milestone or create_milestone. The intent is unambiguous and well-scoped.

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?

There is no explicit guidance on when to use this tool versus alternatives, no prerequisites, and no mention of exclusions. Usage is only implied by the name and the action 'Delete a milestone', which is insufficient for distinguishing appropriate invocation context.

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