getCollateralInfo

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

No annotations provided, so description carries full burden. It adds value by mentioning rate limit (10 req/s) and that borrowing limits are shared across parent and sub-accounts. No contradictions.

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, front-loads the purpose, and includes a rate limit and agent hint. It is efficiently structured for agent use.

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?

For a simple query with one optional parameter, the description covers main use cases and lists key fields. However, without an output schema, it could describe the return structure more fully. Adequate but not exceptional.

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?

The single parameter 'currency' has 0% schema coverage, and the description adds 'Pass currency to filter for a specific coin'. This adds meaning beyond the schema, but lacks format or examples.

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 tool queries collateral information including borrowing rates, limits, and settings, with per-coin data. It is distinct from sibling tools like getBorrowHistory or getAccountInfo.

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 includes an agent hint explicitly stating when to use the tool (check borrowing rates and collateral status) and how to filter with the currency parameter. It lacks explicit when-not-to-use but is sufficient.

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