batch_send

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

Describes sequential dispatch with anti-rate-limit delay and per-target success/error reporting. Also clarifies identity source. No annotations exist, so the description carries the full burden and meets it well, though it could mention partial failure behavior more explicitly.

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?

Three sentences, efficient and front-loaded with purpose. Could be more structured but no unnecessary content.

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?

Covers behavioral aspects like sequential sending, delay, and per-target reporting. No output schema exists, but description hints at return structure. Lacks explicit limits or total time, but adequate for a batch tool of moderate complexity.

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%, so baseline 3. The description reiterates the via='bot' routing already in the schema description but adds no significant new semantic meaning beyond what the schema provides.

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 sends content to multiple targets in one call, distinguishing it from single-target siblings like send_to_user and send_to_group. The verb 'send' and resource 'multiple targets' are explicit.

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?

Explicitly says 'Use for broadcast / fan-out scenarios' and mentions identity handling (cookie user vs bot). It implies when to use but does not explicitly state when not to use or provide alternatives, though the sibling set makes this clear.

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