List Suppressions

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description only needs to add scoping context. It explains that suppressions are listed per message stream with optional filters, but does not describe details like pagination, default behavior, or stream fallback. This is similar to the get_calls calibration case, where scope is added but not deep behavioral traits.

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, front-loaded sentence that conveys the operation and key qualifiers with no redundant wording. Every word earns its 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?

With a well-documented schema (6 optional params, 100% coverage), an output schema, and strong annotations, the description is mostly complete. It could include a hint about common stream_id values or pagination, but these are available in the schema, making the description adequate.

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 every parameter (origin, todate, fromdate, stream_id, email_address, suppression_reason) has a clear description. The main description only says 'optional filters' and does not add meaning beyond the schema, 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 uses a specific verb ('List') with a clear resource ('suppressions') and scope ('for a message stream'). It distinguishes from sibling tools like create_suppressions, delete_suppressions, and list_bounces by targeting suppressions specifically.

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 states clear context ('for a message stream, with optional filters') but does not explicitly mention when to use this tool over alternatives or provide exclusionary guidance. However, the context is sufficient for an agent to infer its list-oriented purpose.

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