delete_global_suppression

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

Without annotations, the description partially discloses behavioral traits: 'Mutating and sensitive' and the confirmation requirement. It does not address irreversibility, auth needs, or edge cases like non-existent emails. Adequate but not rich.

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 two sentences, no extraneous text, and front-loads critical details ('Mutating and sensitive'). Highly efficient.

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 simple delete tool with only two parameters and no output schema, the description covers the essential context: action, confirmation requirement, and sensitivity. Could mention scope (single email) but schema implies it.

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 description adds no new information about parameters beyond what the schema already provides ('email' and 'confirm_delete'). Baseline score is appropriate.

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 explicitly states the action ('remove one email address from global suppressions') and contrasts with siblings like add_global_suppressions and list_global_suppressions. Purpose is clear and specific.

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 the key usage requirement ('Requires confirm_delete: true') and labels the tool as 'sensitive,' implying caution. However, it does not explicitly state when not to use this tool or mention alternatives for bulk operations.

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