delete_release

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

Description emphasizes irreversibility, permanence, and tag deletion ambiguity. No annotations provided, so description compensates well.

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?

Concise 3 sentences, every sentence adds essential information: action and input, behavioral warning, usage guidance. No wasted words.

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?

Covers action, input, irreversibility, side effects (tag deletion), and provides alternative. No output schema needed; context is complete for a delete operation.

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 has 100% coverage with descriptions that include defaults and id clarification. Description does not add new parameter info beyond reinforcing key point, so meets baseline.

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?

Specific verb 'delete' and resource 'release', clarifies input type (numeric id not tag name), distinguishes from sibling tools (update_release with draft, get_release_by_tag).

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?

Explicitly states when to use this tool (confirmed id, irreversible deletion) vs alternative (use update_release with draft to unpublish), and warns about side effects (tag deletion dependent on config).

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