get_crypto_loan_loanable_data

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

No annotations are provided, so the description carries full burden for behavioral transparency. While 'Get' implies a read-only operation, the description does not explicitly state that it has no side effects, nor does it disclose any authentication requirements or rate limits. Minimal disclosure beyond the basic purpose.

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 extremely concise—two lines with a clear header and a bullet-point style. It wastes no words and front-loads the essential information.

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 tool's simplicity (one optional parameter, read-only), the description covers the basics but lacks details about the return structure or data format. No output schema is provided, and the agent could benefit from knowing the typical response fields beyond 'interest rates, limits.'

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 schema describes a single optional string parameter 'currency' with a default of empty. The description adds 'Filter by currency (optional),' clarifying that the parameter is meant for filtering the results. With 0% schema description coverage, this explanation is valuable, though it could include format hints 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 'Get loanable coin data (interest rates, limits).' This specifies the action (Get), the resource (loanable coin data), and the key attributes (interest rates, limits). It distinguishes from sibling tools like get_crypto_loan_borrow_history or get_crypto_loan_collateral_data by focusing on loanable data.

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 does not provide guidance on when to use this tool versus the many other crypto loan tools (e.g., get_crypto_loan_borrowable_collateralisable, get_crypto_loan_position). It mentions an optional currency filter but no context about typical use cases or prerequisites.

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