create_release

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

No annotations are provided, so the description carries the full burden. It discloses the tag prerequisite and optional archive attachment, but does not mention permissions, error behavior if the tag is missing, or side effects beyond creating the release.

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?

Three concise sentences with the action front-loaded. Each sentence adds prerequisite or optional detail without redundancy.

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 no output schema or annotations, the description gives a clear usage scenario: tag existence, required fields, and optional archive. It could mention return value or error handling, but the core selection and invocation information is present.

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?

Input schema covers all 8 parameters with descriptions (100%), so baseline is 3. The description adds value by clarifying that the archive is optional and that tagName must already exist, and by summarizing required fields.

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?

Description explicitly states 'Create a new release tied to an existing Git tag', naming the specific verb (create), resource (release), and binding to a Git tag. This clearly differentiates from sibling tools like update_release, get_release, and create_tag.

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?

It explicitly instructs 'The tag must already exist — use create_tag first if needed', providing when-to-use and an alternative. It also notes required fields (title, description, tag name), which helps select this tool.

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