queryFixedBorrowOrders

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

With no annotations, the description carries full burden. It discloses pagination behavior, filtering capabilities, default and max limits, and account restriction. It does not mention rate limits or authentication, but the information provided is sufficient for basic usage understanding.

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 relatively concise: one sentence for purpose, a bulleted list of rules, and a service line. The service line ('Service: bizasset-uta-loan-prod') is potentially unnecessary. Overall, it is well-structured and front-loaded.

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?

The description explains pagination and filtering but does not mention what fields are returned in the response. Since there is no output schema, the agent is left guessing about the response format. This is a significant gap for a query tool, making it only partially 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 description must compensate. It lists filterable parameters (orderId, orderCurrency, state, term) and cursor/limit but does not explain their meaning or format. The state enum is not described. This adds some value but falls short of fully compensating for the lack of schema descriptions.

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 states 'Query fixed-rate borrow order history', which clearly identifies the verb (query) and resource (fixed-rate borrow order history). It distinguishes from sibling tools like getCryptoLoanFixedBorrowOrderInfo (single order) by implying listing/history. The filtering and pagination rules further clarify its purpose.

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 explicit usage context: cursor-based pagination, filtering options, default page size, maximum limit, and a constraint ('Unified account only'). However, it does not explicitly state when to use this tool over alternatives like getCryptoLoanFixedBorrowOrderInfo or when not to use it.

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