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

Annotations already indicate destructiveHint=true and idempotentHint=true. The description adds behavioral context: 'Edits invalidate affected approvals and the assembled draft' – this explains a side effect of edits on the review state, which is not covered by annotations. It also warns against retrieving emails or inventing codes, which are operational cautions. This goes beyond the annotations and helps the agent understand consequences.

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 two sentences, front-loading the core purpose first and adding cautions second. Every sentence contributes: the first states what it does, the second provides behavioral caveats. It is concise without unnecessary fluff, though it could add more detail on parameters if space allowed.

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?

This is a complex operation with 7 required parameters, nested objects, and no output schema. The description provides only the purpose and a couple of cautions; it does not explain the meaning of key parameters (expectedRevision, fieldIds, includeDefinition, challengeId) or how the code should be obtained and validated. Given the complexity and low schema coverage, the description is insufficient for an agent to correctly invoke the tool without further context.

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 only 29% (only projectId and idempotencyKey have descriptions in the schema). The tool description does not explain any parameters, not even the 'code' mentioned in the purpose, nor expectedRevision, fieldIds, includeDefinition, or challengeId. With such low coverage, the description should compensate but fails to do so, leaving agents to guess the meaning and relationships of the required 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?

The description states a specific action ('Confirm an exact contribution review') with a clear resource ('contribution review') and a distinctive mechanism ('code supplied by the authenticated human reviewer'). It distinguishes itself from other confirm_* tools by specifying 'contribution review' and 'exact', though it does not explicitly name alternatives. The purpose is unambiguous and not a tautology.

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 implies when to use it: when a human reviewer has supplied a code to confirm a contribution review. It also gives a caution ('Do not retrieve the human's email or invent a code'), which guides appropriate use. However, it does not state when NOT to use this tool or mention alternative tools (e.g., helvabase_confirm_review for generic reviews). This leaves some inference to the agent.

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