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

Beyond the annotations, the description discloses important behavior: it burns synth to reduce debt, supports 'all', works with stale prices, checks account limits, simulates first, returns unsigned transaction data for the session key, switches to EIP-712 typed data above the approval threshold, and refuses contract owners. It also clearly states it never signs or sends, which is 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?

The description is front-loaded with the core action and then adds only operationally useful details such as stale-price handling, simulation, approval-threshold behavior, and contract-owner refusal. Every sentence contributes to correct invocation without redundant restatement.

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?

The description is complete enough for a complex prepare tool with nested approval data and no output schema: it explains the two possible return modes and key constraints. It could be slightly richer about the returned transaction/typed-data shape, but the critical behavioral context 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 description coverage is 100%, so the schema already documents the parameters well. The description reinforces the meaning of 'all' and the approval-threshold behavior, but most parameter semantics are already available in the structured schema, making this a baseline 3.

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: burn synth held by a mandate account to reduce its debt, and it explains the returned unsigned transaction or EIP-712 data. It does not explicitly differentiate itself from the sibling prepare_mandate_owner_repay, so it falls short of full sibling-aware clarity.

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 gives some usage context: 'all' repays the whole debt, it works while price is stale, and it refuses when the owner is a contract such as a Safe. However, it does not explicitly say when to choose this tool over alternatives like prepare_mandate_owner_repay, leaving relative usage 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.