get_audience_details

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

With no annotations, description fully covers behavior: read-only, safe to retry, authenticated via API key, max 10 concurrent requests, returns 404 if list_id invalid. All critical traits disclosed.

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 concise and well-structured: purpose statement, usage guidance, behavioral notes, then explicit Args and Returns sections. Every sentence adds value.

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 single parameter tool with output schema, description covers authentication, concurrency, error handling, and return format. No missing information for effective use.

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 for list_id, but description adds full meaning: 'Audience/list ID (10-char alphanumeric, e.g. 'abc123def4'). Obtain from list_audiences.' Completely compensates for schema gap.

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 it retrieves 'full stats, subscribe URL, and rating for a specific audience.' Differentiates from sibling tool list_audiences, which is for browsing all audiences.

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 when you have a list_id and need detailed metrics or the public subscribe URL. Use list_audiences to browse all audiences and discover list_ids instead.' Provides clear when-to-use and alternative.

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