getCryptoLoanCommonMaxCollateralAmount

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

With no annotations provided, the description fully carries the burden. It discloses: private endpoint (authentication required), rate limit (5 requests per time window per UID), behavioral traits (returns 0 if withdrawal would cause liquidation, calculated to maintain LTV below liquidation threshold), and the purpose of preventing liquidation. This is comprehensive.

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 'Features', 'Use Cases', and 'Important' headings. It is front-loaded with the main purpose. It is concise, though there is minor redundancy (e.g., 'Prevents accidental liquidation' and 'Prevent liquidation by validating withdrawal amounts' say similar things). However, it remains efficient.

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 query tool with one parameter and no output schema, the description is complete. It explains the return value (maximum amount or 0 if unsafe), covers authentication and rate limiting, and provides use cases. It adequately informs an AI agent without leaving major gaps.

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?

The only parameter 'currency' is a string. Schema coverage is 0%, so the description should add meaning. However, the description does not explain the parameter beyond its name. The currency is likely the collateral currency, but no details on format, allowed values, or examples are provided. Minimal value added.

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 starts with a clear verb+resource statement: 'Query the maximum amount of collateral that can be redeemed (withdrawn) for a specific currency.' This directly explains what the tool does and distinguishes it from sibling tools like getCryptoLoanCommonCollateralData or getCryptoLoanCommonLoanableData.

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 'Use Cases' section provides clear contexts: 'Check how much collateral can be safely withdrawn', 'Ensure sufficient collateral remains after redemption', 'Prevent liquidation by validating withdrawal amounts'. It does not explicitly list when not to use or alternatives, but the context is sufficient.

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