getCryptoLoanFixedSupplyOrderQuote

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

No annotations provided and description lacks any behavioral traits (e.g., idempotency, side effects, rate limits). As a query tool, it likely is read-only, but this is not stated.

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?

Single sentence, concise but too brief. It could include key details without losing conciseness, but it is not verbose.

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?

With 5 undocumented parameters, no output schema, and many related sibling tools, the description is severely incomplete. Fails to provide enough context for correct invocation.

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?

5 parameters (orderCurrency, term, orderBy, sort, limit) have no descriptions in schema (0% coverage). Description adds no explanation of their meaning or format, leaving the agent without guidance.

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?

Description states 'Query available borrow orders (demand)' but tool name includes 'FixedSupplyOrderQuote', creating confusion. It does not clearly distinguish from sibling 'getCryptoLoanFixedBorrowOrderQuote' which likely handles borrowing quotes. Purpose is unclear.

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?

No guidance on when to use this tool versus alternatives like 'getCryptoLoanFixedBorrowOrderQuote' or other query tools. No context for scenarios or exclusions.

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