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

With no annotations, the description carries the full burden of transparency. It discloses capacity, auto-chunking, and cost via x402, but omits important mutation details such as whether the send is irreversible, failure handling, or that it executes real transfers from the user's wallet. It adds some behavioral context but not enough to fully prepare an agent for side effects.

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 four short sentences, front-loaded with the action, and includes only essential details (capacity, auto-chunking, cost). No wasted words or redundant schema 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?

For a one-parameter tool with no output schema, the description covers key operational aspects: batch purpose, recipient limit, auto-chunking, and cost. It could add when to use for SOL vs tokens or confirm the sending wallet context, but it is largely complete for correct invocation.

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% as the 'recipients' parameter and its nested properties are fully described. The description only reiterates the max count from the schema and adds the auto-chunking behavior, which is not parameter semantics. Baseline 3 is appropriate since schema 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 batches SOL sends to multiple wallets, with the verb 'send' and specific resource 'SOL'. It distinguishes itself from siblings like batch_send_token and quote/status by explicitly indicating SOL, not tokens, and batch sending.

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 gives clear context for when to use (sending SOL to many recipients) and adds practical details like up to 1000 recipients and auto-chunking. It does not explicitly exclude alternatives or mention when not to use, but the context is strong enough for an agent to decide.

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