get_crypto_loan_max_collateral

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

No annotations are provided, so the description carries full burden. It states the action but does not disclose behavioral traits such as whether it is a read-only operation, what the return format is, or if there are any side effects. The term 'max allowed collateral reduction amount' is ambiguous without 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 concise with a single sentence for purpose and a brief args section. However, it could be improved by front-loading the core purpose and perhaps adding structure like 'Returns the maximum amount of collateral that can be reduced for a given loan order.'

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 tool has one parameter, no output schema, and many sibling tools, the description is incomplete. It does not explain what the returned value represents, the type of loan (crypto loan), or any prerequisites. The agent may not understand how to obtain the order_id or what 'max collateral reduction' means.

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 schema description coverage is 0%, and the description adds 'Args: order_id: Loan order ID.' While this clarifies the parameter's type, it does not specify what kind of loan order ID (e.g., ongoing or historical) or provide constraints or format beyond 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 clearly states 'Get max allowed collateral reduction amount for a crypto loan' with a verb and resource. However, it does not differentiate from sibling tools like 'get_crypto_loan_collateral_data' or 'get_crypto_loan_borrowable_collateralisable', which also relate to loan collateral.

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 on when to use this tool versus the many sibling tools. For example, it doesn't contrast with 'get_crypto_loan_ongoing_orders' or explain that this is for reducing collateral on an existing loan.

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