get_email_activity

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

With no annotations, description discloses read-only nature, max concurrent requests, and safe-to-retry. Lacks explicit mention of rate limits or any destructive potential, but it's well-covered.

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?

Concise, front-loaded with purpose, then usage guidelines, then parameter details, then return format. No fluff, every sentence adds value.

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?

Description covers purpose, usage, parameter semantics, and output format. With 3 params, 0% schema coverage, and no annotations, it provides complete context for correct invocation.

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 0%, but description explains each parameter: campaign_id (must be sent campaign), count (1-1000, default 20), offset (pagination hint). Adds constraints and examples beyond 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?

Description clearly states it retrieves per-recipient activity timeline for a sent campaign, with specific actions (opens, clicks, bounces). It also distinguishes from siblings like get_open_details, get_campaign_report, and get_campaign_recipients.

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 provides when-to-use and alternatives (use get_open_details for open data only, etc.). Also mentions authentication (API key), concurrency limit (max 10 concurrent), and safety (read-only, safe to retry).

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