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

Annotations already establish that this is a non-read-only, non-destructive, idempotent write operation. The description adds useful behavioral context not in annotations: repayment consumes wallet tokens and requires an ERC20 allowance for the pool. It does not explicitly state that the tool builds a transaction, but the annotations and output schema mitigate that gap, and there is no contradiction.

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 purposeful sentences: the core operation, the closest alternative, and the required prerequisite checks. Every sentence earns its place and the primary action is front-loaded before routing and checklist details.

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 4-parameter write tool with a full output schema and existing annotations, the description covers the source of funds, prerequisite allowance/approval, debt checking, and the alternative collateral-based path. No critical operational context an agent needs to invoke the tool correctly appears to be 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%, so the schema already documents amount in raw units or 'max_uint256', chain_id defaults, and pool address constants. The description adds that repayment is sourced from wallet tokens and that pool approval is required, but it does not materially deepen the meaning of individual parameters beyond what the schema provides.

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?

Description opens with a specific verb-resource action: 'Repay debt to an Arcadia lending pool using tokens from the wallet' and immediately distinguishes itself from write_account_deleverage, which repays using account collateral instead. This clearly tells an agent what the tool does and how it differs from the closest sibling.

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?

It explicitly states when to use this tool versus the alternative: use write_account_deleverage when repaying with collateral and no wallet tokens. It also provides a concrete pre-flight checklist: check allowance with read_wallet_allowances, approve with write_wallet_approve if needed, and check debt with read_account_info.

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