Delete release

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

Given the annotations already declare destructiveHint: true and readOnlyHint: false, the description adds value by specifying the exact scope of destruction (only release metadata, not the tag). This is beyond what the annotation hints convey, clarifying what is NOT destroyed, which is critical for an agent to predict side effects.

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, focused sentence that front-loads the action and adds essential qualifiers without fluff. Every word contributes to clarifying the tool's scope, making it exceptionally concise and well-structured.

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 relatively simple delete operation with an output schema present and no nested objects, the description is nearly complete. It covers the main action and its boundary condition (not deleting the tag). It doesn't explain return values, but that's acceptable given the output schema. The only minor gap is the lack of parameter context, but this is not critical for a basic delete.

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 33% (only `project` is documented). The description provides no additional insight into parameters, especially the purpose of `acknowledge_release_deletion`, which is a required confirmation flag with no schema description. An agent may not understand why this parameter exists or what value to pass, leaving a gap that the description could have filled.

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 uses a specific verb-resource pairing ('Delete release metadata') and immediately distinguishes itself from the sibling tool `delete_tag` by clarifying it doesn't delete the Git tag with the same name. This clear scoping makes the tool's purpose unambiguous.

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 'without deleting the Git tag' clause provides implicit when-not guidance, signaling to the agent that this tool is for metadata removal only while preserving the tag. While it doesn't explicitly name the alternative (delete_tag), it clearly differentiates the use case, which is highly effective for tool selection.

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