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

Goes well beyond the annotations: it discloses that the call ignores session limits and works with every session key revoked, that it returns UNSIGNED transaction data, that it is simulated first and refused if it would revert, and that it never signs or sends. Those are exactly the traits an agent needs before invoking a prepare-style tool, and they are consistent with readOnlyHint=true and destructiveHint=false.

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?

Four short sentences, front-loaded with what the tool does, then the 'all' special case, then the owner-only behavior, then the return contract. No sentence is redundant and each adds distinct information.

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?

There is no output schema, and the description covers the return (unsigned transaction data, simulated, refused on revert) as well as the execution boundary (never signs or sends). With all four parameters required and fully described, nothing material is missing for a correct call.

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% and each parameter already documents itself, including the 'all' option for tokens. The description reinforces the 'all' semantics and the owner-only constraint but adds no new syntax, formatting, or edge-case detail beyond the schema, so the baseline 3 applies.

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?

Opens with a specific verb and resource: burn synth held by the account to reduce its debt, plus the 'all' shorthand. It also scopes itself as owner-only, which separates it from the session-key path, but it never names the sibling (prepare_mandate_repay) it is the alternative to, leaving the agent to infer the split.

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?

'For the owner only' and 'prepares exactly this one market call and nothing else' give context, and the 'all' behavior is stated. However, there is no explicit when-to-use-this-vs-prepare_mandate_repay rule (e.g. no session key vs. session key), so the routing decision is implied rather than stated.

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