crypto_loan_borrow

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

With no annotations, the description should compensate but fails to disclose behavioral traits such as collateral locking, interest accrual, or LTV management. The user is not informed of side effects or risks, which is critical for a financial mutation tool.

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 brief with a list-style 'Args' section, but it lacks front-loading of key information and a standard structure. It is acceptable but not optimized for quick scanning.

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 lack of output schema and numerous sibling tools, the description is insufficient. It omits details about return values, preconditions (e.g., available collateral), and post-conditions. The agent cannot fully understand the tool's role.

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 description coverage is 0%, but the description adds examples for loan_currency and collateral_currency and mentions the mutual exclusivity of loan_amount and collateral_amount. However, it does not clarify the relationship between these amounts or specify that both are optional but one is required.

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 action 'borrow' and mentions crypto loan, but it does not differentiate from multiple sibling loan borrowing tools (e.g., new_crypto_loan_fixed_borrow, new_crypto_loan_flexible_borrow). The purpose is identifiable but generic.

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 guidance is provided on when to use this tool over alternatives. The description does not mention prerequisites, selection criteria, or context for choosing between loan_amount and collateral_amount. Agents lack direction for correct invocation.

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