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

The description discloses the real consequences of each input value: live:true closes the thread as a won deal and live:false drops the question. This adds meaningful state-change context beyond the annotations, which only flag destructiveHint=true and readOnlyHint=false without saying what is destroyed or changed.

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?

Three sentences, front-loaded with the action, then the consequence of the flag, then the precondition. Every sentence earns its place with no waste.

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 annotations and no output schema, the description covers purpose, input sourcing, side effects, and a usage precondition. It omits permissions/auth requirements, but the core information an agent needs to call it correctly is present.

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 coverage is 100%, so the baseline is 3, but the description adds value: it explains what each value of live actually does (won deal vs. dropped question) and where conversationId comes from, going beyond the schema's terse 'true if the link is on the page' and 'From list_links.'

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 verb and resource: answering a checker's question about a page it could not read, and names the sibling list_links as the source of the input. This is far clearer than a generic 'answer' tool, though it relies on domain jargon ('checker') that an agent must infer from context.

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?

It gives explicit routing ('using a conversationId from the could not read section of list_links') and a precondition ('Only answer after the person has looked at the page, not from a guess'). It doesn't name an alternative tool to use instead, but the sourcing and precondition guidance is strong.

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