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

Goes well beyond the annotations: it discloses that the result is an UNSIGNED transaction (to, data, value, gas), that it is simulated against the latest block and refused if it would revert, and that it never signs or sends. That last clause crucially reconciles readOnlyHint=true with a transaction-producing tool.

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 tight sentences, no filler, with the core action and the return contract front-loaded and the safety semantics immediately after. Every clause carries information an agent needs.

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 prep tool with no output schema, the description covers the return shape, simulation/revert behavior, and non-custodial guarantee. What it omits is whether prior synth approval or balance preconditions matter and which sibling to choose for delegated repayment.

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 still adds value by explaining what the 'all' token value means behaviorally and by tying the tokens argument to the repay(tokens) call. Owner/market semantics are left entirely to 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?

States a concrete verb and resource: burn synth from the wallet to reduce debt, exposing the underlying call repay(tokens). The phrase 'for the user's own wallet' implicitly separates it from the prepare_mandate_*_repay siblings, though it never names them explicitly.

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 'all' special value is explained behaviorally ('repays the whole debt'), which is useful usage guidance. However, there is no explicit when-to-use vs. when-not guidance and no routing to the closest alternatives (prepare_mandate_repay, prepare_mandate_owner_repay) — a real gap given 29 siblings.

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