accountBorrow

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

No annotations provided, so description carries full burden. It mentions rules (variable rate, manual, Unified account) but lacks details on consequences of borrowing, interest specifics, response format, or error conditions.

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 short and to the point, using bullet points for rules. No redundant words, though it could be slightly better organized with parameter explanations.

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 provided. Description omits prerequisites, effect on account, and how to interpret the response. For a mutation tool, more context is needed.

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 has 2 parameters (coin, amount) with 0% description coverage. Description does not explain what coin or amount represent (e.g., symbol, units, decimal precision), leaving the agent without guidance.

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 is for manual borrowing on a Unified account, with specific rules (variable rate only, manual operations only). This distinguishes it from sibling tools like accountFixedBorrow.

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 specifies when to use: for manual, variable rate borrowing on Unified accounts. It implies when not to use (e.g., fixed rate or automated), but does not explicitly mention alternative tool accountFixedBorrow.

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