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

Annotations already mark this read-only and idempotent, and the description is consistent with that by framing it as an 'unsigned' transaction that is 'simulated from the wallet'. It adds real behavioral detail beyond the annotations: the allowlist, write-off, daily-limit, ceiling, LTV, 90% and depth gate checks that will gate the call. It stops short of saying what the prepared output looks like.

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 core action is front-loaded, but the text is a single dense run of unexplained protocol jargon ('write-off', 'the ceiling', 'the market's 90% and depth gate') that slows comprehension. Roughly the right length, but not structured for scanning.

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, so the agent relies on the description for the return value; it only hints at 'unsigned' transactions and 'transactions are built for it to sign' in the schema, without stating whether a submit/broadcast step follows. For a mutating-intent prepare tool with four required params, some call-sequence detail is missing.

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 carries a description, so the schema does the heavy lifting. The description restates the payee constraint ('allowlist, or its owner') and the fact that the tx is built for the wallet to sign, but adds no format or edge-case detail 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 first clause states a concrete action and resource: an unsigned borrow drawn from a credit line and sent directly to a payee. This is clearly distinct from credit_repay, credit_bill, or plain borrow, though the agent has to parse dense jargon ('line', 'USDG goes from Morpho') to get there.

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?

Usage is implied by the mechanics (use this to pay a payee from a line rather than repaying or opening one), and one prerequisite is stated: the `to` must be a factory-confirmed account (isAccount). There is no explicit when-to-use vs when-not or named alternative such as credit_repay or credit_bill.

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