x402_batch_send

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only mentions gas efficiency, a benefit, and does not disclose that this executes an on-chain transaction, whether it is atomic, requires token approval, or has other side effects. This is a significant gap for a payment-sending tool.

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 sentences, front-loaded with the core action 'Send multiple payments' and followed by a key benefit. Every word earns its place, with no filler or repetition.

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?

The schema fully documents inputs, but the description is thin on operational context. It doesn't mention what the function returns, whether it sends real funds, what network it operates on, or any prerequisites like gas or approvals. For a money-moving tool, this under-specification leaves gaps in an agent's understanding.

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?

The input schema already provides descriptions for both parameters (token and payments) with 100% coverage, so the baseline is 3. The description adds no additional parameter-level information beyond what the schema states.

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 'Send multiple payments' which is a specific verb+resource, and adds 'in a single transaction' to distinguish it from single-send tools like x402_send. The contrast with separate sends further clarifies its unique role.

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 phrase 'More gas efficient than separate sends' gives a clear context for when to use this tool: when batching multiple payments is preferable. It implies the alternative (separate x402_send calls) without naming it explicitly, but the guidance is clear enough.

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