postCryptoLoanFlexibleRepayCollateral

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

Beyond the annotations, which already indicate a destructive write operation, the description adds important behavioral context: collateral is auto-converted at market rate and there is a rate limit of 1 request per UID. This gives the agent useful operational expectations without contradicting 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 short, front-loaded with the core behavior, and uses simple bullet points for features. The rate-limit note is useful and non-redundant, and there is no unnecessary 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?

This is a destructive action with no output schema and four required parameters, but the description does not explain the meaning of 'amount', mention whether repayment is partial or full, or describe what response the agent should expect. These are material gaps for a high-risk financial operation.

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 only 25% schema description coverage, the description carries the burden of explaining parameters. It clarifies that collateralCoin is pledged collateral and loanCurrency is the loan currency, but it never defines what 'amount' refers to—whether it is the amount of collateral to convert, the loan amount to repay, or something else. The confirm parameter is already fully described 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 action—repaying a loan by converting collateral into loan currency—and clarifies it uses pledged collateral with auto-conversion at market rate. This clearly distinguishes it from sibling tools like postCryptoLoanFlexibleRepay or accountRepay, which likely use loan currency directly.

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 gives a clear use case: it is 'convenient when lacking loan currency,' which tells an agent when to prefer this tool over direct repayment methods. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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