cm_suppress_emails

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

No annotations (readOnlyHint, destructiveHint) are present, so description bears full responsibility. It states 'Add', indicating mutation, but does not mention side effects (e.g., idempotency, authorization requirements, whether duplicate emails are ignored). This is a significant gap for a mutation tool.

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 sentence that efficiently conveys the tool's purpose. No wasted words.

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?

No output schema is provided, and the description does not explain return values or error conditions. For a tool that modifies state, more context on success indicators, error handling, and what 'suppression' entails (e.g., prevents all emails from client) would be valuable. Given the lack of behavioral transparency and missing output details, completeness is low.

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?

Input schema has 100% coverage, with descriptions for both parameters (clientId and EmailAddresses). The description adds no extra semantics beyond the schema, meeting the baseline.

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 clearly states the action (add) and the resource (suppression list), with specific mention of 'one or more email addresses'. It distinguishes from sibling tools like cm_unsuppress_email and cm_unsubscribe_subscriber.

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 (adding to suppression list) but provides no explicit guidance on when not to use it or alternatives. Could be improved by noting not to use for unsubscribing or removing from suppression.

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