moolah_borrow

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

Annotations indicate destructive=true, readOnly=false. The description adds beyond this by detailing the sequential transaction behavior when both amounts are provided and the LLTV constraint. No contradiction with 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 concise, with four sentences front-loaded with purpose. No wasted words, though slightly more structure (e.g., bullet list) could improve scannability.

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 the complexity of the tool (4 params, no output schema, destructive), the description covers the essential: modes, constraints, and revert behavior. Missing return value info, but acceptable.

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%, baseline 3. The description adds significant meaning by explaining how collateralAmount and borrowAmount interact (one, the other, or both), and the LLTV condition. This goes beyond the schema's 'omit to skip' descriptions.

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's a flexible borrow entry point for Moolah, explicitly describing three usage modes (collateral only, borrow only, both). This differentiates it from siblings like 'borrow' and 'moolah_supply_collateral'.

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 provides clear when-to-use guidance by explaining the three parameter combinations and their effects. It implicitly differentiates from siblings, but does not explicitly state when not to use or name alternatives.

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