Run Outreach Batch

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

The description goes well beyond the annotations, detailing that drafts are generated via MCP sampling, that no API key lives here, that all manual send safeguards still apply, that dry_run defaults to true, that it stops at the daily cap, and that failed drafts are skipped. This is exemplary disclosure for a destructive, non-idempotent 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 organized into clear paragraphs and front-loads the core purpose before explaining mechanics. It is slightly longer than strictly necessary, but every paragraph adds meaningful operational or safety context for a destructive batch tool.

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?

The description covers what happens with drafts, send-path constraints, dry-run behavior, stopping conditions, and failure handling. An output schema exists, so return values need not be described. This is complete for the complexity of the tool.

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 schema already explains all four parameters. The description reinforces dry_run's default safety and mentions daily-cap behavior, but it does not add substantial per-parameter meaning beyond the schema. Baseline 3 is appropriate.

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 opening sentence specifies the verb and resource: 'Draft and send for several leads in one call, unattended.' It clearly distinguishes this batch tool from siblings like send_message and next_outreach_batch by emphasizing unattended multi-lead operation and MCP sampling.

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 clearly conveys context: use this for several leads, unattended, in a scheduled job without human turn-taking. It does not explicitly name alternatives or say 'use send_message for a single lead,' so it stops short of a 5, but the context is unambiguous enough to guide an agent.

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