create_release

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

The description discloses a key side effect beyond annotations: tag creation occurs even for drafts if the tag does not exist. Annotations already indicate non-read-only, but this adds specific behavioral context. No contradiction with annotations.

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 concise with one main sentence and a warning block. Every sentence adds value, and it is front-loaded with the core purpose. Slightly verbose due to the warning, but still efficient.

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?

Given the tool complexity (8 parameters, 4 required), the description covers the primary action and important side effects. An output schema exists, so return value details are not needed. The description is sufficient for an agent to understand the tool's behavior.

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%, so baseline is 3. The description's warning re-emphasizes tag_name and target_commitish behavior already detailed in the schema, adding no new semantics beyond the existing parameter descriptions.

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 states 'Create a new release in a repository' with a specific verb and resource. No sibling tool performs the same action, so it is clearly distinguished.

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 description does not provide explicit guidance on when to use this tool versus alternatives. However, since it is the only release creation tool, usage is implied. No exclusion criteria or when-not-to-use context is given.

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