getCryptoLoanFlexibleAvailableInventory

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

Annotations already indicate readOnlyHint=true and openWorldHint=true, but the description goes further by disclosing how the inventory value is computed, the rounding behavior, and input constraints. This is meaningful behavioral context beyond the annotations.

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 and well-structured: a one-line purpose followed by clear bulleted rules. Every sentence adds useful information with no redundant filler.

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 simple one-parameter read-only query, the description covers input validation, the exact inventory calculation, and rounding precision. It does not describe the response wrapper or whether unavailable coins return zero or an error, but the core semantics are fully specified.

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?

With 0% schema description coverage, the description compensates by indicating the currency parameter is a coin name, must be uppercase, must exist, and must be supported by flexible crypto loan. It does not explicitly say 'currency is the query coin' in the description, but the rules make this reasonably clear.

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 clearly states the tool's action: 'Query available lending pool inventory for flexible loan.' It is specific about the resource being queried and adds the exact computation rule. It does not explicitly name the sibling fixed-loan inventory tool, but the 'flexible loan' qualifier provides enough differentiation.

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 includes practical validation rules: only supported coins, coin must exist, uppercase name. However, it does not explicitly say when to use this tool instead of getCryptoLoanFixedAvailableInventory or other alternative inventory tools. Usage context is implied but not made explicit.

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