prepare_morpho_borrow

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

Annotations already mark destructiveHint as true; description adds that the output is an unsigned transaction and requires collateral. This provides moderate context beyond annotations, but lacks details like error conditions or side effects.

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?

Description is two sentences, front-loaded with the action, and no extraneous information. Efficient but could be slightly more precise about output.

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?

Despite good schema coverage, the tool is complex (borrow transaction preparation) with no output schema. Description fails to mention the output format or that the unsigned transaction needs to be signed/sent, leaving an agent potentially underinformed.

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?

All parameters have descriptions in the schema (100% coverage), so the description adds minimal value. The amount field has an example, but this is already present in the 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?

Description clearly states it builds an unsigned Morpho Blue borrow transaction, differentiating it from sibling tools like prepare_morpho_supply or prepare_morpho_repay. The prerequisite of pre-existing collateral adds 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?

No explicit guidance on when to use this tool versus alternatives. While the mention of required collateral is a precondition, it doesn't help an agent decide between borrow, supply, or other morpho operations.

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