list_saved_audiences

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only states the basic list operation and does not mention that it's read-only, any permission requirements, pagination behavior, or what the return payload contains. The safe-read nature is implied but not explicitly 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?

The description is two concise sentences, with the first stating the core function and the second adding valuable context. There is no redundancy or wasted wording.

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?

The tool is a simple list with optional parameters and no output schema. The description explains what saved audiences are and the listing scope, but it does not mention what fields are returned by default or any edge-case behavior. For a straightforward list tool, it is adequate but not fully complete.

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 has 100% coverage with descriptions for all three parameters (after, limit, fields). The description adds no additional parameter-level insight, so the baseline score of 3 applies.

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 tool's function: 'List saved audiences in the ad account' with a specific verb, resource, and scope. It also adds defining context ('Saved audiences are reusable targeting presets') that distinguishes this from other audience-related tools in the sibling set.

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 for listing saved audiences but does not explicitly tell when to use this versus alternatives like `get_saved_audience` or `list_custom_audiences`. There are no explicit exclusions or alternative references, so the guidance is only implied.

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