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

No annotations are provided, so the description must carry the full behavioral burden. It only says 'suppress' without disclosing side effects, reversibility, idempotency, permissions, or what happens to future sends. This is too opaque for a mutation that could have significant deliverability implications.

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, compact sentence that is easy to parse and front-loads the core action. There is no filler or repetition of schema details, so it earns high marks for conciseness even though it omits behavioral context.

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 mutation tool with no annotations and no output schema, the description is too thin. It does not explain the effect of suppression, whether it can be undone, or what success looks like. The schema covers parameters, but the operational context is missing.

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 coverage is 100%, so the parameters are already documented. The description adds no extra meaning beyond 'active organization', which loosely maps to organization_id. It adds nothing about the optional contact_id or how the email is matched.

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 ('Suppress') and resource (`one recipient`) and scopes the action to the active organization. It distinguishes the action from listing suppressions (commsharbor_suppressions), but does not explicitly clarify what 'suppress' entails (e.g., add to a suppression list).

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 implies when to use this tool (when one recipient needs to be suppressed within the current organization), but it gives no explicit exclusion criteria or comparison to alternatives like commsharbor_deletion_request. The intended use is decipherable but not explicitly guided.

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