get_audience

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

With no annotations provided, the description carries the burden of disclosing behavioral traits. The verb 'Get' clearly indicates a read operation, but it does not explicitly state read-only status, authentication requirements, or behavior on missing IDs. For a benign read tool this is acceptable, but it lacks richer context.

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?

The description is a single, tightly worded sentence that immediately states the tool's purpose. There is zero wasted text, and the structure is direct and front-loaded.

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?

For a simple read tool, the description is adequate but minimal. It does not explain what 'details' includes, nor does it mention error handling or return format, especially with no output schema present. It lacks the richness needed for full contextual completeness.

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?

The input schema already describes both parameters (audience_id and fields) with 100% coverage. The description adds no extra parameter meaning beyond reinforcing 'by ID', which is already in the schema. Baseline of 3 is appropriate.

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 clearly states the action ('Get details') and resource ('specific custom audience by ID'), making it easy to understand. It also distinguishes from sibling tools like list_custom_audiences and get_saved_audience by specifying 'custom audience' and 'by ID'.

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?

The description implies usage when you need details for a single custom audience by ID, but it does not explicitly contrast it with alternatives like listing audiences or getting audience health. No when/when-not guidance is provided beyond the basic read scenario.

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