queryFixedAvailableInventory

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

No annotations are present, so the description carries the full burden. It discloses required parameters, format constraints (uppercase currency), supported coins, formula for inventory, precision handling, and account type restriction. This provides substantial behavioral context.

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 well-structured with a heading and bulleted rules. It is concise, informative, and front-loads the main purpose. Each sentence adds value.

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 provides the inventory formula, precision details, and account restrictions. However, since there is no output schema, it lacks explanation of the return structure. For a query tool, this is a notable gap, but the formula partially compensates.

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% (no parameter descriptions in schema). The description adds that all parameters are required, currency must be uppercase with examples, and implies coins must be supported. However, 'term' and 'annualRate' lack additional semantic detail beyond being required strings.

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 available inventory for fixed-rate borrowing' with specific parameters, clearly indicating the action and resource. It does not explicitly differentiate from sibling tools like 'getCryptoLoanFixedBorrowOrderQuote' or 'queryFixedBorrowMarket', but the purpose is specific enough.

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 usage context (e.g., before borrowing) but does not explicitly state when to use this tool versus alternatives. No 'when not to use' guidance is provided.

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