get_new_crypto_loan_fixed_supply_order

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

The description does not disclose behavioral traits such as side effects (likely none since it's a read operation), error handling, or rate limits. With no annotations, the description carries the full burden but fails to explain what happens for missing orders or limit behavior.

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 concise, with only two sentences for the main purpose and a brief list of parameters. It is front-loaded with the core action, avoiding unnecessary words. However, it could be more structured with separate sections for clarity.

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?

Given the complexity (many sibling loan tools) and absence of an output schema, the description is too brief. It does not explain return values, possible filters, or how to interpret the results. The agent lacks the full context needed to use the tool effectively.

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 coverage is 0% (parameters not described in the main prose). The 'Args' section adds minimal interpretation ('Filter by currency' and 'Number of records'), but does not clarify the meaning of 'order_currency' values or the effect of limit beyond defaults. This is insufficient for a tool with only two parameters.

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 it returns 'fixed crypto loan supply order info', which is specific to retrieving a particular type of order. However, it does not differentiate from sibling tools like get_new_crypto_loan_fixed_borrow_order or get_new_crypto_loan_fixed_supply_market, making selection ambiguous without further context.

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 is provided on when to use this tool versus alternatives (e.g., other loan order retrieval tools). The description lacks context on prerequisites, such as needing an existing order ID or the appropriate market conditions.

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