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

With no annotations, the description carries the full behavioral burden and does a good job: it discloses read-only safety, that data is read live from the sending provider, and that reads are throttled to once per 15 seconds per campaign. It stops short of describing failure modes or permission requirements, which keeps it from a 5.

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?

A single compact sentence that front-loads the returned data and then adds the operational constraints. Every clause earns its place, with no filler.

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 2-parameter, no-output-schema read tool, it covers the important operational context (read-only, live source, throttle) but omits what the filter parameter actually does and gives no guidance about when to choose this over sibling list/stat tools. Adequate but with clear gaps.

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 only 50% (the filter enum is undocumented), so the description should compensate but largely does not. It implicitly maps to the filter values by listing open/click/reply counts, but it never explains what filter does, what the default is, or how 'all' differs.

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 names the exact resource (recipients) and the data returned (open/click/reply counts), so the agent knows this is an engagement-level lead list. It does not explicitly differentiate itself from nearby siblings such as get_campaign_email_stats or list_campaign_emails, but the 'recipients with counts' framing is reasonably distinct.

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 no when-to-use or when-not-to-use guidance and names no alternatives. An agent must infer from the name and sibling list whether this is the right tool for per-lead engagement versus aggregate stats or plain email listing.

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