Abandon Review

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

Beyond the annotations (destructiveHint=true, readOnlyHint=false), the description adds valuable behavioral details: 'history is retained' clarifies that the action is not fully destructive, and 'CONFIRMATION REQUIRED' warns of an extra step. These are useful context the annotations alone do not provide.

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 concise sentences, front-loaded with the confirmation warning. Every word serves a purpose: 'Abandon' states the action, 'in-progress review session' specifies the target, and 'history is retained' clarifies the side effect. No filler or 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?

The tool is simple (one parameter, no output schema), and the description covers the essential purpose and behavioral traits. It could mention the outcome state (e.g., whether the session is marked abandoned) or error conditions, but given the low complexity and the presence of sibling tools for related actions, it is sufficiently complete.

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?

With schema description coverage at 0%, the description must compensate for the parameter. The phrase 'review session' implies that session_id refers to the review session being abandoned, but it does not explicitly state that session_id is the identifier to use. Given the parameter name and format, the meaning is mostly inferable, but the description adds only marginal semantic value.

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 uses a specific verb 'Abandon' with a clear resource 'an in-progress review session', and explicitly distinguishes the action from completing or deleting by adding 'history is retained.' This makes the tool's purpose unmistakable, especially alongside sibling tools like complete_review and start_review.

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 provides clear context: it is for abandoning an in-progress review session, implying it should be used when you want to stop without completing. The 'history is retained' note adds important usage context. However, it does not explicitly mention alternatives like complete_review or state when not to use it.

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