github_delete_release

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

With no annotations, the description carries the full burden of behavioral disclosure. It does disclose a crucial non-obvious behavior: the tag is not deleted. However, it does not mention permission requirements, irreversibility, effects on assets, or what happens if the release does not exist, leaving gaps for a mutation tool.

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 extremely concise: one line stating the core action and a key exception, followed by a structured argument list. Every element adds value with no redundancy or filler.

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?

The description is thin for a destructive operation. It explains the tag retention behavior but omits permission requirements, side effects (e.g., deletion of release assets), and error handling. Given that an output schema exists, return values may be handled, but the lack of behavioral context makes it only minimally complete.

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 0%, so the description must compensate, but it merely lists the parameter names without explaining their meaning or format. The parameter names are somewhat self-explanatory, but release_id is not clarified (e.g., numeric ID vs. tag name), and session_name is not explained. This adds minimal value beyond the schema.

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 a release) and identifies the specific resource with a key distinction from siblings: the tag is NOT deleted. This differentiates it from other delete tools like delete_repo or delete_branch without ambiguity.

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 is provided on when to use this tool versus alternatives such as github_delete_repo or github_delete_branch. The description does not mention prerequisites, error conditions, or any context that would help the agent decide between deletion tools.

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