Post Instances Payouts Evm

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

Annotations only declare the safety profile (write, open-world, non-idempotent, non-destructive); the description adds genuinely new behavioral facts: a 5-minute quote expiry, the retry/replay contract, the token-approval prerequisite, and deterministic dev-instance outcomes (66600 fails, 77700 refunds). These are exactly the traits an agent cannot derive from the annotation block.

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?

Front-loaded with the core action, then caveats, then timing, then test-mode behavior — a sensible order with no filler sentences. Slightly dense for one short paragraph, and the dev-instance test values sit oddly at the end, but every sentence carries actionable information.

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 nested-body mutation with no output schema and thin parameter documentation, the description covers the critical gaps: expiry, idempotency, approval prerequisite, and test-mode outcomes. What is missing is what the call returns (payout object/id) and the error path for an expired quote.

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 only 33%, and the description compensates only indirectly: it explains the managed-wallet funding case, which points to wallet_id over sender_wallet_address, without stating the either/or explicitly (the schema does that). It also references 'request_amount 66600/77700', a field that is not in the input schema at all, which muddies rather than clarifies parameter meaning.

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+resource ('Executes a payout quote') and immediately disambiguates the misleading 'Evm' name by scoping it to payouts funded from a BlindPay-managed wallet on any network. It partially differentiates from siblings (PayoutsSolana, PayoutsStellar) by naming the self-custodied EVM case, but never explicitly says which sibling handles the self-custody path, so routing is still partly inferred.

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?

Gives clear preconditions: quote must not be expired (5-minute window), Idempotency-Key should be sent on any retry risk, and self-custodied EVM wallets must approve the token before calling. It stops short of naming the alternative endpoint for self-custodied wallets, so the when-not branch is implied rather than explicit.

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