Manage Releases

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the description does not need to re-state that. It adds nothing beyond them: no statement that delete is irreversible, no note that create requires tag_name (only in schema), no auth or rate-limit context. For a destructive multi-action tool this is thin.

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 short sentences, front-loaded with the resource and operation list, no filler. Slightly wasteful because the verb list repeats the action enum already visible in the schema.

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?

Eleven parameters across six action modes is non-trivial, but the schema carries the per-action parameter mapping well and there is no output schema to explain. What is missing is behavioral context a caller needs for a destructive dispatcher: which actions need write scope, whether delete can be undone. Adequate, with clear gaps.

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 100% and the schema itself documents per-action requirements (tag_name 'required for create', releaseId 'required for get, update, delete', target_commitish/generate_release_notes 'create only'). The description only mentions the action field, which the schema already explains. Baseline 3 applies.

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?

Names the specific resource (GitHub Releases) and enumerates the six operations, which line up exactly with the action enum. It is distinguishable from siblings by resource, though the 'manage_' prefix pattern shared with manage_issues, manage_prs, etc. means the only differentiator is the noun.

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?

Tells the agent to use the action field to select the operation, which is minimal routing guidance, but gives no when-to-use or when-not-to-use context, no prerequisites (e.g. permissions to create/delete releases), and does not point to any alternative tool or mention that get_latest differs from list+filter.

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