borrow

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

Discloses that only variable rate is supported and stable is deprecated, and authentication via PRIVATE_KEY env var. No annotations provided, so description carries full burden and does well.

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?

Three concise sentences, front-loaded with purpose, no redundancy. Every 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?

No output schema, but description doesn't explain return values or consequences of borrowing (e.g., debt accrual). Adequate for a simple action but could be more complete.

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%, so baseline is 3. Description adds 'in human units' for amount and repeats asset description. Minimal added value 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?

The description clearly states 'Borrow an asset from Tydro', specifies the action (borrow), resource (asset), and distinguishes from sibling tools like supply, withdraw, and repay.

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 states prerequisites (existing collateral, PRIVATE_KEY env var) and constraints (only variable rate mode 2 supported, stable deprecated). Clear when to use and when not, but no explicit alternative for stable rate borrowing.

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