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

Goes well beyond the annotations: discloses zero Panda fee, that output is unsigned transactions ordered plus a single EIP-5792 batch, that they are simulated from the wallet, that a sign_url exists for a human owner, and that nothing is sent. The 'nothing is sent' statement is consistent with readOnlyHint=true on a build-only 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 tightly packed sentences, front-loaded with purpose and scope, then economics, then return shape. No filler and every clause carries 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?

With no output schema, the description compensates fully by describing the return payload (ordered unsigned txs, EIP-5792 batch, sign_url, simulated) and the no-send/no-fee behavior. An agent has everything needed to call and interpret this tool.

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 both parameters and the "all" pattern are already documented. The description restates the asset and the part-or-all notion in prose, adding only marginal meaning over the schema. Baseline 3 is appropriate.

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?

Names a specific verb (repay), the exact protocol and market (Morpho WETH/USDC), the asset (USDC), and the scope (part or all). An agent can immediately separate this from siblings like build_borrow or build_lend_supply.

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?

"Repay part or all of the USDC owed" implies when the tool applies, but there is no explicit when-not guidance or routing to alternatives (e.g. how it relates to build_withdraw_collateral for unwinding, or prerequisites like an existing borrow position). Usage is inferable but not stated.

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