getCryptoLoanFixedBorrowOrderQuote

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

No annotations are provided, so the description carries the full burden. It discloses that it is a public endpoint, has a rate limit (1000 requests per time window), and that results show actual supply orders with potential rate changes. It does not mention idempotency or safety, but the context is adequate for a read-only query 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 well-structured with sections for features, use cases, and important notes. It front-loads the purpose. While some redundancy exists (e.g., features and use cases overlap), each section adds value and the overall length is appropriate.

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?

The tool has 5 parameters (0 required) and no output schema. The description explains its role in the borrowing flow but lacks details on parameter constraints and return value structure. It mentions results but not their format, leaving some ambiguity for an agent to use the tool effectively.

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 input schema has 5 parameters with 0% description coverage. The description mentions the ability to filter by currency and term and sort by rate or amount, but does not map these to specific parameter names or provide details for parameters like limit. Given the low schema coverage, the description should provide more parameter-level 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 the tool queries available supply orders for a specific currency and term. It specifies the verb 'Query' and the resource 'supply orders (lending offers)', distinguishing it from sibling tools like postCryptoLoanFixedBorrow or getCryptoLoanFixedSupplyOrderQuote.

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 provides explicit context for when to use the tool: 'View available lending offers before placing borrow order' and lists use cases. However, it does not explicitly state when not to use it or compare to alternative tools, though the sibling differentiation is implied.

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