update_release

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

With no annotations provided, the description carries full burden. It discloses the need for write permission and implies a partial update pattern. It does not detail side effects or response behavior, but it adequately sets expectations 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 a single sentence followed by a field list. It wastes no words, front-loads the action, and lists all relevant fields. 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?

Given no output schema, the description does not explain the return value. However, it covers all input parameters and usage hints. It is nearly complete for a simple update tool, missing only details about the response.

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?

The input schema has 100% coverage, describing each parameter. The description adds value by explaining the 'updates' object contains only fields to change, reinforcing the partial update semantics. This improves usability beyond the schema alone.

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 'Modify an existing release.' The verb 'modify' and resource 'release' are specific. The list of updateable fields distinguishes it from sibling tools that operate on different resources (e.g., manual runs, sessions).

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 instructs to 'Send only the fields you want to change inside the `updates` object,' which guides partial updates. It also mentions 'Requires write permission.' However, it stops short of explicitly stating when not to use or alternatives like creating a new release.

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