add_suppression

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

The description explicitly states that the address 'can never be emailed', clearly indicating an irreversible destructive action. This compensates for the lack of annotations. However, it does not detail permissions or side effects beyond the result.

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 a single concise sentence (13 words) that front-loads the purpose and example. 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?

Given the tool's simplicity (2 params, no output schema), the description adequately covers the core functionality. It could mention the absence of a return value or error scenarios, but it is complete enough for selection and invocation.

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 baseline is 3. The tool description does not add additional meaning beyond the schema definitions, though the schema itself is descriptive enough.

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 'suppress an address' and its consequence 'so it can never be emailed', with an example 'opt-out request'. It distinguishes this tool from siblings like list_suppressions and remove_suppression.

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 a use case (opt-out request) but does not explicitly state when to use this tool versus alternatives like unsubscribe_contact, or mention any prerequisites or exclusions.

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