claim_leverage_liquidation

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

No annotations provided, so description carries full burden. Only mentions state conditions but lacks disclosure of side effects, permissions, rate limits, or return value. Minimal behavioral context beyond prerequisites.

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?

Two efficient sentences: first states purpose, second adds conditions and parameter note. Front-loaded, no wasted words, easy to parse.

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 one-param tool with no output schema, the description adequately covers core purpose, usage conditions, and parameter clarification. Could mention post-claim effects but still sufficient for agent selection.

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 coverage is 100% with description 'Leverage position ID (from get_leverage_positions)'. Description adds value by clarifying it's loanId NOT hubId, which compensates for any potential confusion.

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?

Clearly states the action (claim) and resource (USDB residue from a liquidated leverage position). Explicitly mentions 'leverage' to distinguish from other claim tools. No ambiguity.

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?

Specifies prerequisites: position must be already liquidated and have non-zero claim. Also clarifies parameter usage (loanId not hubId). Does not explicitly compare with sibling 'claim_liquidation' but conditions are clear.

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