github_issues_delete_milestone

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

With no annotations, the description carries full burden for behavioral disclosure. It only says 'Delete a milestone' with no additional context about side effects (e.g., does it cascade to issues?), required permissions, or irreversibility. This is insufficient for safe usage.

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 short sentence (3 words). While concise, it is too brief and omits necessary details. It does not waste words but also does not provide enough information to be useful on its own.

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 no output schema, no annotations, and tautological schema descriptions, the description is incomplete. It does not mention return values, error conditions, required privileges, or how to obtain milestone_number. For a simple delete operation, more context is expected to avoid misuse.

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 descriptions for parameters are tautological (e.g., 'owner' -> 'owner'), providing no real semantic value. The tool description adds no further clarification on how milestone_number is defined (it is typed as string but typically numeric). With 100% schema coverage but useless descriptions, the description fails to compensate.

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 (milestone). It is unambiguous but could be more specific by clarifying it refers to issue milestones (e.g., 'Delete an issue milestone from a repository'). The tool name and sibling context help, but on its own it is clear.

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 provided on when to use this tool versus alternatives like github_issues_update_milestone or github_issues_create_milestone. There is no mention of prerequisites, effects on issues associated with the milestone, 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.