prepare_morpho_supply

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

Discloses key behaviors beyond annotations: deposits loan token, may emit approve tx, returns handle + preview for Ledger signing. Annotations already indicate destructive and idempotent, but description adds valuable implementation detail.

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?

Two well-structured sentences front-load purpose, then cover inputs, optional behavior, and output. No redundant information; each sentence earns its place.

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?

Given 100% schema coverage and no output schema, the description fully covers inputs, behavior (approve tx), and output (handle + preview). Complete for the tool's complexity.

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 has 100% coverage with good descriptions; description adds meaning by noting amount is human-readable (not wei), supports 'max', and explains approvalCap defaults and options. Adds clarity beyond 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?

Clearly states the tool builds an unsigned Morpho Blue supply transaction for depositing loan tokens to earn lending yield. Distinguishes from siblings like prepare_morpho_borrow by specifying 'supply' and mentioning that market params are resolved on-chain from market id.

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?

Explicitly lists required parameters (wallet, marketId, amount) and optional approvalCap with usage notes. Mentions that insufficient allowance triggers an ERC-20 approve transaction and how to cap it. Does not explicitly state when not to use, but context is clear.

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