postCryptoLoanFlexibleRepayCollateral

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

No annotations exist, so the description bears full responsibility. It mentions auto-conversion and a rate limit, but omits critical details like what happens to collateral after conversion, any fees, prerequisites, or error scenarios.

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 two sentences and bullet points for features. No redundant information, though it could benefit from a bit more structure.

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 no output schema and sparse parameter info, the description should cover more behavioral aspects. It lacks explanations for return values, minimum amounts, or implications of the action.

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 coverage, the description must explain parameters. It does not define what `amount` refers to (loan repayment amount or collateral amount) and lacks details for `loanCurrency` and `collateralCoin`.

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 it repays a loan by converting collateral to loan currency, with features like auto-conversion at market rate. This distinguishes it from other loan repayment tools like `postCryptoLoanFlexibleRepay` which likely uses direct loan currency.

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?

It mentions 'Convenient when lacking loan currency' which provides a clear use case, but does not explicitly state when to avoid this tool or compare it to alternatives.

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