get_campaign_locations

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

With no annotations, the description fully discloses behavior: read-only, safe to retry, max 10 concurrent requests, data aggregated from IP geolocation at open time. 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 brief purpose, usage notes, Args/Returns sections. Slightly verbose but efficient for the information density; earns its sentences.

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 input, output (with Returns section), constraints, and alternative. Output schema exists but description adds clarity. Complete for a read-only reporting tool.

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?

Despite 0% schema description coverage, the description provides detailed parameter info: campaign_id format and requirement, count range and default, offset usage. Adds value beyond schema titles.

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 action: 'Retrieve geographic open data for a sent campaign, broken down by country and region.' It identifies the specific resource (campaign) and output structure, distinguishing it from siblings like get_domain_performance.

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?

It provides explicit use cases ('region-targeted follow-ups, timezone-aware sending'), conditions ('Only works for sent campaigns'), and an alternative tool ('Use get_domain_performance for per-provider stats instead'). Includes authentication and rate limits.

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