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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The single sentence states the action but does not disclose whether suppression is permanent or reversible, whether it is idempotent for already-suppressed recipients, whether it halts in-flight campaigns, or what the tool returns. For a mutation operation with zero annotation coverage, this is a significant gap.

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 efficiently front-loaded with the verb and resource, and every word earns its place with no fluff or repetition of schema content. It is arguably too terse given the missing behavioral context, but as a concise statement of intent it is well-structured.

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?

Given that this is a mutation tool with no annotations, no output schema, and many confusingly similar siblings, the description is incomplete. An agent cannot determine the side effects of suppression, how it differs from unsubscribe or deletion tools, or what happens after a successful call. The definition needs at least usage context and behavioral expectations to be 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%, so the schema already documents all three parameters (email, contact_id, organization_id) clearly, setting the baseline at 3. The description's phrase 'in one organization' adds marginal reinforcement that organization_id scopes the operation to a single org, but it doesn't explain how contact_id interacts with email or when the optional contact_id is needed.

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 ('Suppress') with a clear resource ('a recipient') and a scope qualifier ('in one organization'), so an agent can tell what action this performs. However, it doesn't explicitly differentiate itself from behaviorally adjacent siblings like commsharbor_preference_unsubscribe, commsharbor_deletion_request, or commsharbor_audience_member_remove, so it falls short of full sibling differentiation.

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 suppression versus alternatives such as preference_unsubscribe (marketing opt-out), deletion_request (data erasure), or audience_member_remove (list removal). With over 100 siblings including several related suppression/deletion/preference tools, the agent is left to infer the right context with no exclusions or alternative routing.

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