list_audiences

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to mention pagination behavior despite the presence of limit and offset parameters, does not clarify whether 'all' implies multiple pages, and does not describe the return structure or any side effects. This leaves the agent uncertain about how results are delivered.

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 concise sentence with no redundant phrases or filler. It directly communicates the purpose without unnecessary detail.

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 that there is no output schema and no annotations, this minimal description is insufficient. It does not explain the response format, pagination implications, or how to interpret 'all' in light of the limit/offset parameters. For a list operation, more context about pagination and result structure is needed.

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 100% for all three parameters, so the schema already documents the meaning of user_db_id, limit, and offset. The description adds marginal context by indicating the list is scoped to a user database via user_db_id, but does not provide any additional semantics for limit/offset beyond the schema.

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 'List all audiences in a user database' clearly states the action (list), the resource (audiences), and the scope (all, within a user database). This distinguishes it from sibling tools like get_audience which retrieves a single 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?

No guidance is provided on when to use this tool versus alternatives such as get_audience, nor are there any notes on prerequisites or exclusion criteria. The description simply states what the tool does without any contextual 'use this when' direction.

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