get_campaign_report

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

Annotations already declare readOnlyHint=true. Description adds that it's a 'high-level overview' and only works for sent campaigns. This is valuable context beyond annotations, but doesn't detail failure modes or post-conditions for unsent campaigns.

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?

Description is concise: one-line summary, then usage hints, parameter details, and return format. Every sentence adds value, no fluff. Front-loaded with key info.

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?

Given the output schema (explicitly listed return fields), annotations, and sibling tools, the description covers all necessary aspects: parameters, constraints, return structure, and alternatives. No missing context for effective 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 coverage is 0%, so description must compensate. It adds helpful meaning for campaign_id (format 'abc123def4', prerequisite sent status, source). However, the optional account parameter is not described, leaving a gap. Overall adds some value but incomplete.

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 explicitly states 'Retrieve aggregate performance metrics for a sent campaign', using a specific verb and resource. It distinguishes from sibling tools by directing to get_campaign_click_details, get_open_details, and get_campaign_recipients for different granularities.

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?

Clear when to use: only for sent campaigns. Provides explicit alternatives (get_campaign_click_details for per-link data, get_open_details for per-recipient opens, get_campaign_recipients for delivery status) and instructs how to obtain campaign_id via list_campaigns(status='sent').

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