list_audiences

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

The GET method and 'List' verb communicate that this is a read-only enumeration, which is useful given no annotations are provided. However, the description does not disclose pagination behavior, default limits, ordering, or response shape, so the tool's behavior beyond the basic HTTP method remains opaque.

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, front-loaded sentence with no filler or repetition. It is efficient, though arguably too terse to fulfill the informational burden for a tool with three undocumented parameters and no annotations.

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 absence of annotations, output schema, and parameter documentation, the description is incomplete for safe and correct use. It lacks pagination semantics, return-value expectations, and any mention of rate limits or access requirements.

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 description coverage is 0% and the description adds no meaning for the after, limit, or before parameters. An agent cannot infer how pagination works or what values these parameters expect from either the schema or the description.

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 uses a specific verb ('List') and resource ('audiences'), and adds the HTTP GET endpoint, making its intent unambiguous. It is clearly distinct from sibling tools like create_audience, get_audience, update_audience, and delete_audience, though it does not explicitly contrast with get_audience.

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?

There is no guidance about when to use this tool versus get_audience or other listing tools, and no mention of pagination use cases or exclusions. The usage context is only implied by the word 'List,' providing no practical selection guidance.

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