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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partially covered. The description adds genuinely new behavior: the deletion cascades to signatures built from the group, all members lose signatures, and the action is irreversible — details not derivable from the annotations alone.

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?

Three short sentences, zero filler, and the most important information (cascade scope and irreversibility) is placed up front where the agent will act on it before invoking the tool.

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 single-parameter destructive tool with full schema coverage and no output schema, the description covers the critical unknowns: what else gets destroyed, who is affected, and that the operation cannot be reversed. Nothing an agent needs before calling it is missing.

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?

There is a single required 'id' parameter and schema description coverage is 100%, with the schema itself pointing to list_groups as the source. The description adds no format, prefix, or sourcing guidance beyond what the schema already provides, so the baseline of 3 applies.

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?

States a specific verb and resource ('Delete a group') plus the cascade scope ('AND the signatures built from it'), which clearly separates it from siblings like update_group or remove_teammates_from_group. The scope qualifier is front-loaded and unambiguous.

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?

Destructive intent is implied and the consequence ('Everyone in it loses their signature. Cannot be undone.') steers the agent toward caution, but there is no explicit when-to-use/when-not guidance or mention of alternatives such as update_group for reversible changes. Usage is inferred rather than stated.

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