get_campaign_abuse_reports

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

Annotations already indicate readOnly and non-destructive. Description adds authentication via API key, max 10 concurrent requests, and retry safety. Adds value beyond annotations without contradiction.

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?

Every sentence serves a purpose: purpose, usage, alternatives, behavioral notes, parameter docs, return format. Well-organized and succinct without redundancy.

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?

Covers all essential aspects: purpose, usage context, alternatives, authentication, concurrency, parameters, return structure. Even though output schema exists, description still summarizes return fields clearly.

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?

With 0% schema description coverage, description provides full parameter meaning: campaign_id source (list_campaigns or search_campaigns) and account usage with environment variable naming and fallback. Compensates well for missing schema descriptions.

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?

Clearly states verb 'List' and resource 'abuse complaints against a sent campaign'. Differentiates from siblings get_campaign_abuse_report (single complaint) and get_campaign_report (overall stats).

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 says when to use: 'monitor deliverability health'. Provides alternatives: 'Use get_campaign_abuse_report for a single complaint's details. Use get_campaign_report for overall stats.'

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