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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds meaningful context beyond that: it returns live on-chain state and enumerates the possible lifecycle states (not opened, OPEN, MET, RELEASED, RETURNED, CANCELLED), which helps the agent interpret results.

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?

A single well-structured sentence front-loads the resource and address, then lists the returned facets. It is efficient and wastes little, though the trailing state enumeration makes it slightly dense.

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, the description carries the burden of describing return values and does so by naming terms, asset, amount, arrival status, and state. Combined with the 100%-covered input schema, an agent has enough to invoke and interpret it correctly; minor gaps like error or not-found behavior remain.

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% and the single 'vault' parameter is fully documented with pattern and origin (from ifso_prepare_v2_payment). The description's phrase 'by its payment address' maps to the same field without adding syntax or format detail beyond the schema, so the baseline 3 applies.

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 retrieval action ('One v2 if-so payment by its payment address') and enumerates what is returned: terms, asset and amount, arrival status, and on-chain state. The 'v2' qualifier and payment-address key distinguish it from the sibling ifso_get_payment and align it with ifso_prepare_v2_payment.

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?

Usage is implied by the 'v2' naming and the schema note pointing to ifso_prepare_v2_payment, but there is no explicit when-to-use guidance or mention of alternatives like ifso_get_payment or ifso_explain_payment. An agent must infer the choice from names alone.

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