prepare_morpho_supply

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

Goes beyond annotations: discloses that an ERC-20 approve tx may be emitted first, explains approvalCap behavior, and mentions returns a handle+preview for Ledger signing. No contradiction with annotations (destructiveHint=true consistent with write).

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?

Four well-structured sentences with key info front-loaded. No redundancy; every sentence adds value. Efficient and clear.

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?

Covers essential aspects for a transaction-building tool. Lacks explicit mention of return value shape (only mentions 'handle + preview'), but sufficient given no output schema and many sibling tools.

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?

Adds significant meaning beyond schema: clarifies amount is human-readable (not wei), 'max' for full balance, and provides detailed guidance on approvalCap options. Schema coverage is 100%, but description enhances usability.

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 clearly states it builds an unsigned Morpho Blue supply transaction, depositing the market's loan token to earn lending yield. It distinguishes from sibling tools like prepare_morpho_borrow by specifying supply verb and market context.

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 describes when to use (supply to Morpho Blue), mentions prerequisite allowance handling and chain limitation (only ethereum). Lacks explicit exclusions or alternatives, but adequate for selection among many siblings.

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