delete_group_suppression

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It flags the action as mutating and sensitive and highlights the confirm_delete requirement, but does not detail other traits such as return value, irreversibility, or authentication needs.

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 concise sentences: first states purpose and sensitivity, second states a necessary requirement. No fluff, front-loaded with the verb 'remove', making it efficient for an AI agent to parse.

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 deletion tool with three simple parameters and no output schema, the description covers the core action and a key constraint. However, it lacks details on success/error behavior, idempotency, or side effects, which would be valuable for an agent.

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 each parameter. The description adds emphasis on the confirm_delete constraint ('Must be true'), but adds little beyond the schema for email and group_id. Baseline 3 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 clearly states the verb (remove), resource (one email address from a suppression group), and an important constraint (requires confirm_delete: true). It distinguishes from sibling tools like delete_global_suppression or add_group_suppressions by specifying the scope.

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 explicitly states it's for removing one email from a suppression group and that it's mutating and sensitive. However, it does not explicitly list alternative tools for similar tasks or specify when not to use this tool, though the name and context make it reasonably clear.

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