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

Annotations provide little (only readOnlyHint=false, openWorldHint=true, destructiveHint=false), so the description must carry the burden. It discloses the fail-closed exclusivity gate, the response names the serving model, and the pricing (15 MESH/call). These go beyond annotations and are important for correct invocation. No contradiction with 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 dense but efficient. It front-loads the purpose and model, then contrasts with pos-rescue, then gives input/output shape. Every sentence adds information; no filler. It's longer than a one-liner but appropriately so given the behavioral and pricing details.

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?

Given the nested input schema (fully described) and no output schema, the description compensates by specifying the output structure. It also covers the exclusivity gate, pricing, and model choice. It doesn't mention edge cases (e.g., empty trouble) but the schema handles those. For a commercial tool with clear contract, this is complete enough for an agent to call 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?

Schema coverage is 100%, so baseline is 3. The description adds value by outlining the output structure ({rescue: {diagnosis, plan, workaround, cautions}, exclusivity_checked, model, next}) which is not in the schema (no output schema). It also reiterates the fail-closed exclusivity semantics, reinforcing the schema's own description. This is meaningful addition beyond the schema.

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 identifies this as the smart tier of pos-rescue, specifically for harder integration knots, served by a more capable model. It explicitly contrasts with the sibling pos-rescue (fast default), so an agent knows exactly what this tool is for and how it differs.

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 states that pos-rescue is the fast default and this is for harder integration knots, giving an explicit when-to-use versus the alternative. The phrase 'stays the fast default' implies this tool is for when that default isn't enough, which is clear guidance.

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