prepare_morpho_supply_collateral

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

Annotations already indicate destructive and idempotent behavior. The description adds value by revealing that an approval step may be included, which is a key behavioral nuance beyond the annotations.

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 description is two concise sentences, front-loading the core purpose (building a supplyCollateral transaction) and adding the notable approval step behavior without filler.

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 transaction-building tool with 5 parameters and no output schema, the description covers the essential function and behavior. It could be slightly more complete by explicitly stating it does not execute the transaction, but that is implied by 'build an unsigned transaction'.

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% with detailed parameter descriptions. The description adds minimal extra meaning beyond confirming the approval step, so baseline score is appropriate.

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 the tool builds an unsigned Morpho Blue supplyCollateral transaction to add collateral, distinguishing it from sibling tools like prepare_morpho_supply (loan supply) and prepare_morpho_withdraw_collateral (collateral removal).

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?

The description implies usage for adding collateral but does not explicitly contrast with alternatives (e.g., prepare_morpho_supply for loan supply or prepare_morpho_withdraw_collateral for removal). An agent might benefit from explicit when-to-use guidance.

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