batch_transfer_erc20

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

With no annotations provided, the description must disclose behavioral traits itself. It only states the action and a benefit, but fails to mention that this is a transaction (requires gas, may fail), whether token approval is needed, atomicity of the batch, or what happens on partial failure. The return type is not described. The privateKey security note is in the schema, not the description, so the description adds minimal behavioral transparency.

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 a single concise sentence (10 words) that immediately conveys the core function and a key advantage. Every word contributes value, and it is front-loaded with the action and resource. No fluff or repetition of schema details.

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?

Given this is a transaction tool with no output schema and no annotations, the description should provide more context: what it returns (e.g., transaction hash), prerequisites (approval/balance), atomicity, and error behavior. The schema is detailed for parameters, but the description does not address these operational aspects, making it incomplete for an agent to use confidently.

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 description coverage is 100%, so the baseline is 3. The description adds the notion of 'multiple recipients' which clarifies the recipients array purpose, but it does not add detail beyond what the schema already provides for network, privateKey, or tokenAddress. The description's contribution to parameter semantics is minimal.

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 action (transfer ERC20 tokens), the resource (ERC20 tokens), and the specific scope (multiple recipients in a single transaction). It distinguishes from the single-transfer sibling (transfer_erc20) and highlights gas efficiency, but does not explicitly name an alternative to differentiate against.

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 'multiple recipients in a single transaction' implies when to use this tool (for batch operations) and the gas-efficiency benefit implies a preference over individual transfers. However, it does not explicitly state when NOT to use it or mention alternatives like transfer_erc20, leaving the guidance 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.