get_eepurl_activity

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

With no annotations, description provides full behavioral context: authentication via API key, max 10 concurrent requests, read-only safe to retry, and requires sent campaign with tracking enabled.

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 clear sections and front-loaded summary. Slightly verbose but justified by providing complete information.

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 1 parameter and presence of output schema, description covers all needed info including return structure, constraints, and usage context.

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 has 0% coverage; description adds an example value and constraint (must be a sent campaign) to campaign_id, adding meaning beyond type and required status.

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 social sharing stats for a campaign's eepurl' with a specific verb and resource, and distinguishes from sibling tool get_campaign_click_details.

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?

Clearly states when to use (to measure sharing stats via Twitter/Facebook) and when not (use get_campaign_click_details for in-email clicks). Also notes prerequisite: sent campaign with eepurl tracking enabled.

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