get_campaign_report

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

No annotations provided, so description fully handles behavioral disclosure. It states 'Read-only, safe to retry' for idempotency, 'Authenticated via API key. Max 10 concurrent requests' for auth and rate limits, and documents return structure. No contradictions.

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?

Well-structured with separate sections for summary, alternatives, constraints, arg, and returns. Slightly verbose with 'High-level overview.' but all content is valuable. Could be trimmed slightly but overall efficient.

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?

Despite output schema existing, description already covers return structure in detail. Includes authentication, rate limits, preconditions (sent campaign), and parameter guidance. No missing elements for confident use.

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 0%, but description fully documents the sole parameter: provides type, example value ('abc123def4'), validation requirement ('Must be sent'), and source ('Obtain from list_campaigns(status="sent")'). Exceeds bare 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?

The description clearly states the tool retrieves aggregate performance metrics for a sent campaign, listing specific data points (opens, clicks, bounces, benchmarks). It distinguishes itself from sibling tools like get_campaign_click_details, get_open_details, 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 tells when to use this tool vs alternatives: 'Use get_campaign_click_details for per-link data, get_open_details for per-recipient opens, get_campaign_recipients for delivery status.' Also states it only works for sent campaigns, providing clear exclusions.

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