queryFixedBorrowMarket

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

Annotations already declare readOnlyHint=true and openWorldHint=true, lowering the burden on the description. The description adds meaningful behavioral details: default sort is ascending, sort=1 means descending, maximum 100 results per request, and only unified accounts can use it. These go beyond the structured annotations.

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 compact and well-structured: a clear opening sentence followed by bulleted rules. The Service line is minor but not distracting. It front-loads the core purpose and then lists constraints efficiently.

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 read-only market query with no output schema, the description covers the most important behavior and constraints. Still, the meaning of the `term` parameter is left unexplained, and there is no guidance on how this tool relates to similar fixed-loan query tools, leaving moderate gaps.

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%, so the description must compensate. It explains the orderBy enum values (apy, term, quantity), sort semantics, and the result limit. However, it does not explain what the `term` parameter itself represents or what values orderCurrency accepts, leaving meaningful gaps.

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 a specific action and resource: 'Query the fixed-rate borrow market (supply order book) to see available lending offers.' This conveys the tool's role as a market-data query and distinguishes it from order-management siblings, though it does not explicitly name an alternative tool.

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 gives useful usage rules such as orderCurrency being required, sort behavior, maximum 100 results, and the unified-account-only constraint. However, it does not explicitly explain when to choose this tool over similar siblings like queryFixedBorrowContracts or getCryptoLoanFixedAvailableInventory.

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