x402_send

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

With no annotations provided, the description carries the full burden of disclosure. It only states that it sends a payment, but does not disclose that it will create an on-chain transaction, incur gas fees, require a funded wallet, or be irreversible. No details about error conditions or network behavior are given, which is insufficient for a mutating financial 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?

The description is extremely concise: two short sentences that clearly state the action and supported tokens. There is no unnecessary fluff or repetition; every word earns its place.

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 payment tool with 4 parameters, no output schema, and no annotations, the description is too thin. It does not explain what the tool returns (e.g., transaction hash), any prerequisites like wallet setup, network specifics, or potential failures. The minimal description leaves many essential context gaps unfilled.

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%, with each parameter having a description (e.g., 'Token to send', 'Amount to send'). The description adds minimal extra meaning, such as confirming that native tokens are supported, but does not provide additional syntax or semantic details beyond the schema. Baseline 3 applies because the schema already does the heavy lifting.

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's function: sending a direct cryptocurrency payment to an address, and specifies supported token types (USDs, native). However, it does not differentiate itself from closely related siblings like x402_send_payment or x402_batch_send, leaving ambiguity about the exact scope.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention that it is for single direct payments, nor does it exclude batched or gasless variants, which are present in the sibling list. The description implies usage only through the verb 'send' without context.

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