mailkite_list_suppressions

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

The description complements the readOnlyHint annotation and adds useful behavioral context beyond it, such as the management session token requirement and the fact that suppressed addresses cause sends to be dropped. It does not contradict the read-only annotation; the token requirement does not imply mutation.

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 two sentences with no filler, front-loading the core action 'List suppressed addresses' before supporting details. Every sentence earns its place by adding either scope, consequences, or a prerequisite.

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 zero-parameter read-only list tool, the description covers the resource, the specific suppression types, the operational consequence of suppression, and the required auth token. It omits response format details, but no output schema exists and the information provided is sufficient for an agent to call it correctly.

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 has zero parameters and an empty input schema, so there is nothing for the description to document about parameters. The baseline of 4 is appropriate because the description adds no misleading parameter information and the schema is fully covered.

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 states a specific verb ('List') and resource ('suppressed addresses'), and names the categories (unsubscribes, hard bounces, spam complaints, manual) that define the scope. This clearly distinguishes it from sibling tools like mailkite_add_suppression and mailkite_remove_suppression, which mutate the same 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?

The description provides clear context by explaining that sends to suppressed addresses are dropped before delivery, which tells an agent why listing suppressions is useful before sending. It also states the prerequisite 'management session token,' but it does not explicitly mention alternatives or when not to use this tool.

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