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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered structurally. The description adds genuine context beyond that with the `full_access` key prerequisite, but says nothing about the paginated response shape, ordering, or result-set size — meaningful gaps for a list operation.

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?

Two short sentences, front-loaded with the resource and followed by the operational prerequisite and endpoint. Zero padding; the only miss is that it omits useful pagination behavior rather than being overlong.

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?

There is no output schema, so the description should hint at what a list call returns (items array, has-more/cursor semantics), and it does not. The auth note is helpful, but for a cursor-paginated list tool the definition is only minimally 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?

Schema description coverage is 100% and each of the three pagination params is documented in the schema, including the mutual-exclusion rule between `after` and `before`. The description adds no parameter semantics at all, so the baseline 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 says "List audiences" plus the API endpoint and operationId, which is a specific verb+resource but largely restates the tool name and title. It does nothing to distinguish this from siblings like get_audience or list_contacts, so an agent must infer the collection-vs-single difference from names alone.

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 only guidance is the auth requirement ("Requires a `full_access` API key"). It never states when to use this versus get_audience, nor does it mention pagination navigation as a use case, so there is essentially no when-to-use framing.

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