queryFixedBorrowContracts

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

Discloses key behavioral traits: cursor-based pagination, filterability, default/max page size, output includes principal/interest/status, and unified account only. No annotations provided, so description carries the burden, and it does well.

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?

Description is concise with a clear introductory sentence followed by bullet-point rules. No redundant information; each sentence adds value.

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 query tool with no output schema and no annotations, the description provides adequate context: output fields, restrictions, and service. Missing some details like error handling or authorization, but sufficient for typical use.

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 has 0% description coverage. The description compensates by explaining filter parameters (orderId, orderCurrency, term) and pagination parameters (limit, cursor). Adds meaning beyond the raw schema.

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 it queries fixed-rate borrow contracts for matched loan details. However, it does not explicitly distinguish from sibling tools like getCryptoLoanFixedBorrowContractInfo, leaving some ambiguity.

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?

Lists rules such as pagination, filters, defaults, and account type. Provides some guidance on usage but lacks explicit when-to-use or when-not-to-use compared to alternatives.

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