Lends Prepare Repay

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds that this only constructs a transaction rather than executing one, and clarifies that the amount is a maximum cap. It does not describe the returned transaction object or any required approval step, but the annotation coverage lowers the burden.

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?

A single, tightly worded sentence with an active verb and no filler. The important qualifier 'maximum raw amount' is included, making it both concise and information-dense.

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 simple two-parameter tool with safe annotations, the description conveys the core action adequately. Still, an agent is left to infer what collateral refers to semantically, whether prior approval is needed, and what the constructed transaction contains. The lack of an output schema makes the missing return-shape detail more noticeable.

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 0%, so the description needed to explain both required parameters. It only adds meaning to maxAmount ('maximum raw amount'), giving units and cap semantics, but it never explains what collateral represents beyond the address pattern in the schema. This under-compensates for the complete lack of schema-level parameter descriptions.

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 uses a specific verb ('Construct'), names the exact resource ('leUSD repayment transaction'), and includes a distinguishing detail ('maximum raw amount'). This clearly separates it from sibling prepare tools such as borrow, deposit, withdraw, and stake.

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: an agent should use this when a leUSD repayment transaction needs to be constructed. However, the description does not mention prerequisites such as an existing debt or approved leUSD allowance, nor does it contrast this with related tools like lends_prepare_approve_leusd_for_repay.

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