get_audience_activity

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

Annotations already declare readOnlyHint=true, so description doesn't need to reiterate. Description adds valuable context: pagination details (count, offset), return structure (JSON with total_items and activity array), and field semantics (day, emails_sent, etc.). 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: purpose, usage guidance, parameters, returns. Each section is concise and informative. No fluff. Front-loaded with the most important 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?

Description covers purpose, parameters, return structure, and alternatives. Missing explanation for the 'account' parameter, but since it's optional and likely obvious from context, the gap is minor. With output schema present, lack of full return description is acceptable.

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%, so description must compensate. It describes 3 out of 4 parameters (list_id, count, offset) with format, examples, and constraints. The 'account' parameter is missing from the description, which is a minor gap. Overall adds significant meaning beyond the 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?

Description clearly states 'Retrieve the recent daily activity for an audience' with specific verb and resource. It explicitly distinguishes from get_audience_details and list_campaigns, listing what those alternatives provide.

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 states when to use: 'to inspect an audience's day-by-day engagement history over its recent lifetime.' Also provides clear alternatives: 'use get_audience_details for aggregate stats and list_campaigns for per-campaign performance.'

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