delete_release

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

Beyond the destructiveHint annotation, the description discloses the important side effect: the tag is not automatically deleted and is only removed when delete_tag is true. It also explains the rationale about not moving commit history, which is exactly the kind of behavioral context 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?

Two sentences with no padding. The primary action is front-loaded, and the second sentence adds valuable side-effect context without unnecessary detail.

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 destructive 4-parameter tool with annotations and an output schema, the description is nearly complete. It defines the action, the default behavior, and the optional tag-deletion flag. Minor omissions like permission requirements are not critical given the simple API shape.

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 description coverage is only 25%, and the description partially compensates by clarifying the release/tag relationship and the meaning of delete_tag. The repo owner and repo name parameters are standard and self-explanatory, so their lack of detail is not a serious gap.

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?

States a specific verb and resource: 'Deletes a release.' It also distinguishes itself from tag-only deletion by explaining that the tag survives unless the delete_tag flag is set, which separates it clearly from the sibling delete_tag tool.

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 gives useful context about the release/tag relationship but does not explicitly say when to choose delete_release over alternatives like delete_tag or update_release. The intended use is implied rather than directly stated.

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