release_approve

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

Without annotations, description only states the immediate effect (clear gate, advance nodes). Does not disclose potential side effects, reversibility, error states, or permission requirements.

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?

Single sentence with no superfluous text. Efficient and direct.

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 output schema, description doesn't mention return format or behavior. For a tool with two required parameters and multiple siblings, more detail is needed for an AI agent to use it correctly.

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?

Only one parameter ('gate') is illustrated with an example ('qa-signoff'), but 'coordinate' is not explained at all. Schema coverage is 0%, so description fails to adequately define both parameters.

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?

Clearly states the tool clears a manual gate and advances blocked nodes, using specific verb 'clear' and resource 'manual gate'. Differentiates from siblings like release_bump or release_start by focusing on gate approval.

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?

No explicit guidance on when to use this tool versus alternatives. Siblings are listed but no differentiation criteria or prerequisites provided.

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