queryFixedBorrowMarket

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

No annotations provided, so the description carries full burden. It discloses that results are limited to 100, sorting behavior, and that it requires a unified account. However, it does not mention read-only nature, permissions, or other potential side effects.

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 with a main sentence and bullet points for rules. Every sentence adds value, and the structure is clear and front-loaded. No redundant 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 no output schema, the description lacks details about the return structure of lending offers. It does provide the service name for tracing, but omits error handling, permissions, or response format, leaving some gaps for a 5-parameter tool.

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 coverage is 0%, but the description adds meaning by explaining the sorting fields (apy, term, quantity), sort direction values ('0' ascending, '1' descending), and the max limit. The term parameter is mentioned but not fully detailed (e.g., expected format).

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 the fixed-rate borrow market (supply order book) to see available lending offers. It uses a specific verb and resource, and distinguishes from sibling tools like getCryptoLoanFixedBorrowContractInfo which target different aspects.

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 rules for usage (required params, sorting, limits, unified account) but does not explicitly guide when to use this tool versus alternatives. It lacks exclusion criteria or references to sibling tools for different use cases.

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