create_release

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

Annotations declare idempotentHint=false, but the description claims 'a retry after a half-finished release recovers' and that an existing tag's release is updated instead of rejected. That is an idempotency/retry-safety claim that contradicts the annotation. While the upsert detail is otherwise valuable, the direct conflict forces a score of 1.

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: the first front-loads the main action, the second adds a high-value retry/upsert behavior with a cross-reference. No fluf. Every sentence earns its place.

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?

Despite having an output schema and annotations, this is a 9-param mutation tool with zero schema descriptions. The overview is too terse to be complete: no parameter semantics, no routing vs update_release/create_tag, and a conflicting retry claim. Agents could easily call it incorrectly.

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%; the description compensates for none of the 9 params. It never explains make_latest's enum, generate_release_notes behavior, draft/prerelease flags, or required body/release_name semantics, leaving an agent to guess at important inputs.

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 ('Creates a new release') and then adds a crucial distinguishing nuance: an existing tag's release is updated rather than rejected. This separates it from sibling tools like get_release and update_release without needing to inspect their schemas.

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 intended use is implied: call this to create a release, and a retry after a half-finished release should work. However, it never explicitly names alternatives or says when NOT to use it, e.g. when update_release or create_tag would be a better choice.

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