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

Annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful domain context by explaining that suppression entries are addresses and domains that are never emailed, but it does not disclose pagination behavior, filtering behavior, or return structure beyond that concept.

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 extremely short and contains no wasted words, but it is a noun phrase rather than a front-loaded action statement. It is concise to the point of under-specification for an AI agent that needs to confirm the tool's operation.

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 simple list tool with rich annotations and a fully described schema, the description gives enough conceptual context to understand what is being listed. However, with no output schema, it should arguably mention that the response is a paginated list of suppression entries and what kinds of values are returned.

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%, so the three parameters (q, limit, cursor) are fully documented in the schema. The description adds no parameter-specific meaning, which sets this at the baseline for well-covered schemas.

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 identifies the resource semantically (addresses and domains never emailed), but it does not explicitly state that the tool lists or retrieves suppression entries. Combined with the name and title the purpose is inferable, but the description itself does not provide a clear verb+resource statement or distinguish this from sibling tools.

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 on when to use this tool versus alternatives such as add_suppression or list_email_status. The description only defines the concept of a suppression list, leaving the agent to infer that this is a read/list operation and when it should be preferred.

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