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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful behavior: it returns unsigned transactions for signing, is refused with a worded error when nothing is kept, waits when the payee is frozen (PayeeFrozen), and is simulated from the wallet. That is real disclosure beyond the safety hints, though return shape details are absent.

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?

Information-dense and reasonably front-loaded, with every clause contributing detail about assets or failure modes. It is a single long, heavily nested sentence that is harder to parse than necessary, so it falls just short of a 5.

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 4-parameter preparation tool with full schema coverage and no output schema, the description covers the qualifying condition, defaults, token variants, and failure modes (nothing kept, PayeeFrozen). The main remaining gap is the shape of the unsigned transaction output, which is acceptable given there is no output schema.

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%, so the baseline is 3, but the description adds meaning beyond the schema: `token` is explained as one token type per claim (USDG, bUSDG, held vault shares, stock-symbol shares, or address), and `to` defaults to the wallet and must not be frozen. This improves on the schema without fully restating it.

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?

States a specific verb (claim/take) and resource (a bailout payment a v2 trade account keeps) and immediately clarifies that it produces unsigned transactions rather than executing anything. This distinguishes it from the sibling `bailout`, `bailouts`, `bailout_offer` and `bailout_repay` tools without requiring the schema.

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 the qualifying condition (a payment the wallet could not take because USDG froze it or the token refused) and that one claim is needed per token, which implies when to use it. However, it never names an alternative sibling or says when to use `bailout` / `bailout_offer` / `bailout_cancel` instead, so routing is left to inference.

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