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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds genuinely new context beyond the annotations: result ordering (newest first) and the meaning of 'pending' vs 'active'. It does not mention pagination behavior or what a result row contains, so it adds some but not rich value.

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?

A single compact sentence with the core purpose and ordering front-loaded, and the status glossary folded in efficiently. The trailing 'Free.' is terse billing context that earns minimal but some place.

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 read-only list tool with five parameters, no output schema, and low schema coverage, the description should at least explain that query is a search filter and that limit/offset paginate. Those gaps mean an agent can identify the tool but may misuse the filtering and paging parameters.

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 coverage is only 20% (only the newsletter param is described), so the description must compensate. It does clarify the status enum semantics (active=confirmed, pending=not yet confirmed), which the bare enum does not, but leaves limit, offset, and query (search) completely unexplained in both schema and 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?

States the resource being listed (subscribers of a newsletter) and the ordering (newest first), which clearly distinguishes it from newsletters_invite and newsletters_remove_subscriber. The phrasing 'Who is on a newsletter' is informal but unambiguous about the verb+resource.

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 explicit guidance on when to use this versus the sibling subscriber tools, nor any note about prerequisite setup or when filtering by status is appropriate. The status list implies a filtering capability but nothing tells the agent when to apply it.

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