getCryptoLoanFixedSupplyOrderQuote

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description needs less safety disclosure. It adds useful context by framing the data as 'available borrow orders (demand)' in the market, but it does not disclose quoting behavior, result variability, pagination, or other operational traits. This is acceptable but not rich.

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?

A single, front-loaded sentence with no filler. Every word adds meaning: 'Query', 'available', 'borrow orders', 'demand', and 'in the market' are all relevant to purpose and context.

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 tool with five undocumented optional parameters, no output schema, and a large set of similar siblings, the one-line description is insufficient. It explains what the tool is for but not how to filter, sort, limit, or interpret results. An agent would need external documentation to invoke it correctly.

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% for five parameters (sort, term, limit,, orderBy, orderCurrency), and the description provides no parameter-level meaning. It does not compensate for the schema gaps, leaving an agent without crucial details like allowed values, format, or how ordering and currency filtering behave.

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 uses a specific verb ('Query') and resource ('available borrow orders (demand) in the market'), which clearly communicates the tool's function. It does not explicitly differentiate from sibling tools like getCryptoLoanFixedSupplyOrderInfo, but the added '(demand)' clarifies the supply-side perspective.

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 implies the tool is for browsing available borrow orders in the market, but it gives no explicit when-to-use guidance, exclusions, or alternatives. An agent must infer the appropriate context from the tool name and domain, making this minimally adequate but not directive.

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