get_audience_details

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

Discloses read-only nature, safe to retry, returns 404 for invalid list_id, max 10 concurrent requests, and API key authentication. No annotations provided, so description fully covers behavioral aspects.

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 separate sections for purpose, usage, authentication, and parameter/returns. Every sentence is necessary and informative without being verbose.

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 the tool's simplicity (1 parameter, clear purpose), description covers all needed context: what it does, when to use, parameters, return fields, and error handling. Output schema exists but description adds field names.

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?

Only parameter list_id is described with format (10-char alphanumeric), example, and source (list_audiences). Input schema only has type string, so description adds significant value.

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 'Retrieve full stats, subscribe URL, and rating for a specific audience.' Uses specific verb and resource, and distinguishes from sibling tool list_audiences by indicating when to use each.

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 (have a list_id, need detailed metrics) and when not (use list_audiences to browse). Also mentions authentication, concurrency limits, and error behavior.

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