get_audience_activity

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

Annotations provide readOnlyHint, idempotentHint, destructiveHint. Description adds 'Authenticated via API key. Max 10 concurrent requests. Read-only, safe to retry.' Extends beyond annotations with concrete behavioral constraints.

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 efficient, front-loaded with purpose, then usage, behavior, parameters. No fluff. Each sentence serves a purpose.

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?

With 4 parameters (1 required), output schema exists, description explains return format and fields. Covers all necessary context for invoking correctly.

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%, but description includes detailed 'Args:' section explaining each parameter: list_id (format, example, source), count (range, default), offset (pagination), account (optional, configuration, referral). Adds meaning beyond 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 (opens, clicks, sends, subscribes) for an audience.' It specifies verb and resource, and distinguishes from siblings like get_audience_details and list_campaigns by mentioning their use cases.

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 'Use to inspect an audience's day-by-day engagement history' and provides 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.