add_global_suppressions

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

The description labels the tool as 'Mutating' which hints at a write operation, but no annotations are provided to confirm safety. It does not disclose side effects, duplicate handling, permissions, or reversibility (the existence of a deletion sibling is not referenced).

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 extremely concise (5 words) but lacks structure and context. It is front-loaded with 'Mutating:' but provides no further detail, making it under-specified.

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 has one parameter, no output schema, and no annotations, the description should provide more behavioral context. It fails to explain return values, error conditions, or any side effects of the mutation.

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?

With 100% schema coverage, the parameter description already specifies 'Email addresses to suppress globally'. The tool description adds no additional meaning beyond this.

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 ('email addresses to global suppressions'). It distinguishes from sibling tools like add_group_suppressions and delete_global_suppression through the 'global suppressions' qualifier.

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?

No guidance is provided on when to use this tool versus alternatives like add_group_suppressions. There is no mention of prerequisites, frequency limits, or context for use.

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