queryFixedBorrowOrders

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds useful behavioral detail beyond them: pagination style, page-size limits, supported filter dimensions, and account-type restriction. Nothing in the description contradicts 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 compact and front-loaded with the purpose, then uses scannable rule bullets. The final 'Service:' line adds limited value for an agent but is minor overhead rather than a significant defect.

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 history query with all-optional parameters, the main constraints are covered: pagination, filters, page size, and account restriction. However, since there is no output schema, the state enum values and the cursor/pagination response behavior are left underspecified, making the description adequate but not complete.

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 text must compensate. It identifies which parameters can filter and that limit has a default/maximum, but it does not explain cursor format, term semantics, or state enum values, leaving most parameters effectively undocumented for an agent.

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 opens with a specific verb and resource: 'Query fixed-rate borrow order history.' This clearly separates it from sibling tools like getCryptoLoanFixedBorrowOrderInfo (single order lookup) or queryFixedBorrowMarket (market data), even without naming them explicitly.

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 rule bullets give concrete invocation context: cursor-based pagination, filters by orderId/orderCurrency/state/term, page size bounds, and unified-account restriction. It does not name alternatives or explicit when-not conditions, but the intended use is evident from the description.

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