getCryptoLoanFlexibleAvailableInventory

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds meaningful detail: supported coins only, uppercase requirement, the exact availability formula, and rounding behavior ('borrow precision, rounded down'). This is strong, though it does not explain error cases or the response shape.

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 compact, front-loaded with the main purpose, and the bulleted rules are scannable and free of filler. Every sentence adds information an agent needs.

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 one-parameter query tool with no output schema, the description is largely complete: it defines input constraints and the exact meaning of the returned inventory value. It does not explicitly describe the response format, but the formula and precision rules make the behavior sufficiently clear.

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%, so the description must compensate. It does by explaining that the single 'currency' parameter must be an existing, uppercase coin supported by flexible crypto loan. This adds meaning beyond the bare string type in the schema.

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 a specific verb ('Query'), a specific resource ('available lending pool inventory'), and a specific product type ('flexible loan'). This clearly distinguishes it from sibling tools like getCryptoLoanFixedAvailableInventory and getSpotMarginTradeFlexibleAvailableInventory.

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 phrasing 'for flexible loan' implies when to use this tool, and the rules list validity constraints. However, it does not explicitly contrast with alternatives or state when not to use it, so guidance is implied rather than explicit.

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