batch_send_erc20

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

No annotations provided. Description discloses automatic token approval and required private key, adding behavioral context beyond the schema. However, lacks details on failure handling or idempotency.

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, each essential. Front-loaded with purpose, then prerequisites and fee. No wasted words.

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 schema covering all params and no output schema, the description provides necessary context (network, approval, fee). Could mention return value or error conditions, but overall sufficient.

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 covers all three parameters with descriptions. The description does not add new information beyond the schema; the 'human-readable' note for amounts is already in schema.

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?

Clearly states it sends ERC-20 tokens to multiple recipients in a single transaction on Base. Distinguishes from sibling tool batch_send_eth by specifying ERC-20.

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?

Provides prerequisites (DEPLOYER_PRIVATE_KEY) and fee, but does not explicitly state when to use this tool versus siblings like batch_send_eth or estimate_batch.

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