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

Annotations already declare the read-only, idempotent, non-destructive profile, so the bar is lower; the description still adds real value by explaining the coverage semantics (matches, seen in last day, notifications withheld) and how negated=true renders as != in the rule expression. It does not address auth, rate limits, or pagination, keeping it below 5.

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?

Purpose is front-loaded, followed by return-value semantics and then the call-ordering workflow. Mostly every sentence earns its place, though the expression/negation aside is dense for an agent that may not need to render the rule verbatim.

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 no output schema, the description correctly carries the burden of describing the return shape and coverage fields, and it supplies the follow-up workflow. The remaining gap is that it never contrasts with the sibling list_suppressions, which an agent selecting among 60+ tools would need.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify here.

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 a specific verb and resource ("List the suppression rules of the caller's account") and details what each returned rule contains. However, it never distinguishes itself from the near-identical sibling list_suppressions, leaving the agent unable to tell the two apart without inspecting schemas.

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?

Explicit when-to-use ("Call this first when asked why an issue is missing from a list or why a card never arrived") and clear routing to the follow-up tool (manage_suppression_rule with action=delete/update/preview/create). No when-not guidance and no mention of the alternative list_suppressions, so it falls short of a full 5.

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