queryFixedBorrowContracts

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

Annotations already establish read-only and open-world behavior, and the description builds on that by adding concrete constraints: cursor-based pagination, default and maximum page sizes, filterable fields, and a unified-account restriction. No side effects are hidden, and there is no contradiction with the 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 a compact set of bullets with the core action first and no filler. Each line adds a distinct, useful fact, and the service line is cleanly separated.

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 query tool with no output schema, the description covers purpose, filters, pagination, account scope, and return fields, which is adequate for basic invocation. It lacks explicit guidance on cursor format, filter combination semantics, and sibling differentiation, which would be needed for full self-sufficiency among many closely related loan tools.

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 carry parameter meaning, and it largely does: orderId, orderCurrency, and term are named as filters, limit is tied to page size defaults, and cursor is tied to pagination. It stops short of specifying value formats, cursor encoding, or whether filters can be combined, but it provides enough semantic grounding for correct invocation.

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?

States a specific verb ('Query') and resource ('fixed-rate borrow contracts'), with 'matched loan details' clarifying the domain. However, it does not explicitly differentiate itself from sibling tools such as getCryptoLoanFixedBorrowContractInfo or queryFixedBorrowOrders, so an agent must infer the list-vs-detail distinction.

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?

Provides useful operational context: supported filters, pagination limits, and the 'Unified account only' restriction. It does not name any sibling alternatives or state when to choose this tool over similar loan query tools, leaving tool selection partly to inference.

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