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

Annotations already convey idempotentHint=true and destructiveHint=false. The description adds beyond that: it clarifies the action is a release (non-destructive), requires an idempotency_key, and notes that item_texts are 'Display only' and 'Ignored by the server.' It also instructs the agent to show the display field verbatim in a code block, which is behavioral guidance not present in annotations. No contradiction exists between description and 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 compact—five short sentences with no filler. The purpose is front-loaded, followed by usage, then a specific display instruction. It avoids redundant detail already in the schema. It earns a 4 rather than a 5 because it slightly repeats the idempotency requirement that is also in the schema and could be tightened, but overall it is well-structured and 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?

For a mutation tool with an output schema and annotations covering idempotency and non-destructiveness, the description covers purpose, usage context, required parameters, and a special output instruction. It does not explicitly mention the alternative item_ids parameter, but that is already fully described in the schema. The description is complete enough for an agent to invoke correctly without needing to infer missing details.

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 all parameters are already documented in the schema. The description adds minimal value: it repeats that item_numbers are required and that idempotency_key is needed, but it does not explain item_ids or item_texts beyond what the schema already states. The only extra is the instruction to show the display field, which pertains to output rather than parameters. Per the rubric, with high coverage the baseline is 3, and the description does not meaningfully elevate it.

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 a specific verb ('Releases') and a specific resource ('picked items back to todo'). It also gives a concrete use case: 'Use if you picked the wrong item or need to release work.' This distinguishes it from siblings like cherry_pick (which does the opposite) and complete_items (which marks done), so an agent can select it correctly without inspecting schemas.

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 explicitly says when to use it ('if you picked the wrong item or need to release work') and lists prerequisites ('Requires idempotency_key') and required input ('Pass item_numbers of the picked items'). It does not name alternatives or exclusions, but the context is clear and the sibling list includes cherry_pick, making the contrast obvious. This earns a 4 rather than a 5 because it stops short of explicitly saying 'do not use for X.'

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