Execute liquidation

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

With no annotations provided, the description carries full burden but only states the action without disclosing behavioral traits. It doesn't mention permissions required, whether liquidation is irreversible, potential side effects (e.g., collateral seizure), rate limits, or error conditions. This is inadequate for a mutation tool with significant financial implications.

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 a single, direct sentence with no wasted words. It's front-loaded and appropriately sized for the tool's name and title, making it easy to parse quickly.

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 complexity of a liquidation operation, no annotations, low schema coverage, and no output schema, the description is incomplete. It lacks details on behavior, parameters, outcomes, and context, leaving significant gaps for an AI agent to understand and invoke the tool correctly.

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?

Schema description coverage is low at 25%, with only 'id' documented. The description adds no parameter semantics beyond the schema, failing to explain 'collateralAsset', 'repayAmount', or 'minCollateralOut'—critical for understanding liquidation mechanics. It doesn't compensate for the coverage gap.

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 'Liquidate a lending loan' clearly states the action (liquidate) and target (lending loan), but it's vague about what liquidation entails and doesn't differentiate from sibling tools like 'strato.cdp.liquidate' or other lending operations. It provides basic purpose but lacks specificity about scope or mechanism.

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 is provided on when to use this tool versus alternatives like 'strato.cdp.liquidate' or other lending tools such as 'repay' or 'withdraw-collateral'. The description offers no context about prerequisites, timing, or exclusions for liquidation.

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