Withdraw queued payouts (v2)

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

Annotations already indicate not read-only and not destructive. The description adds context: why payouts are queued (e.g., blocklisting token) and that it withdraws the queued balance. This goes beyond annotations, though it does not detail side effects like reversibility or fees.

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, moderately long sentence that front-loads the action. It contains no fluff and earns its place, but splitting could improve readability.

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?

With no output schema and two simple parameters, the description explains the scenario adequately. However, it omits details like idempotency (though in annotations), error conditions, and the exact process. The scope limitation to Sepolia is not reflected in the schema, which could lead to incorrect usage.

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 50% (token has a description). The description adds meaning to the chain parameter by restricting to Sepolia, but this contradicts the schema enum. For token, it adds little beyond the schema. Overall, it provides some value but with inconsistency.

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 the tool checks a queued balance and withdraws it, with a specific scenario (settlement payout could not be delivered). It distinguishes from siblings like p2p_claim_default by focusing on unclaimed payouts. However, it says 'v2 chains (Sepolia) only' while the schema accepts other chains, creating potential confusion.

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 explains when to use (when a settlement payout could not be delivered) and limits to v2 chains (Sepolia). It does not explicitly mention alternatives or when not to use, though context implies it's for queued payouts only.

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