list_suppressions

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. While 'List' implies a read-only operation, the description does not mention pagination behavior, ordering, return format, or any side effects. It adds no behavioral context beyond the obvious action.

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 a colon-delimited list. Every word earns its place, and the key information is front-loaded with the verb 'List'. There is no unnecessary fluff or repetition.

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 read-only tool with two optional parameters and no output schema, the description is largely complete. It identifies the resource, the kinds of suppressions, and implicitly what the tool does. Minor gaps remain regarding the meaning of 'limit' and any return value structure, but these are not critical for basic usage.

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?

The description compensates for the 0% schema coverage by enumerating the allowed values for the 'kind' parameter (unsubscribes|bounces|blocks|spam_reports|invalid_emails), which are not defined as enums in the schema. However, it does not explain the 'limit' parameter, leaving its meaning to inference from the default value.

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 clearly states the tool lists a suppression list and enumerates the five kinds (unsubscribes, bounces, blocks, spam_reports, invalid_emails). This gives a specific verb, resource, and scope, and helps distinguish it from siblings like add_suppression or check_suppression, though it does not name them explicitly.

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 description offers no guidance on when to use this tool versus alternatives such as check_suppression, add_suppression, or remove_suppression. It simply states what it does without context, prerequisites, or exclusions, leaving the agent to infer usage purely from the tool name and sibling list.

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