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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond that by enumerating the group categories that will cause the call to be rejected, which the annotations cannot express. It does not say what happens to attendees assigned to the deleted group or what the failure mode looks like.

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?

Two sentences, zero filler: the action is front-loaded and the blocking constraints follow immediately. Every clause earns its place.

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?

An output schema exists, so return values needn't be described, and annotations cover safety semantics. The remaining gap is what happens to dependent data (attendee membership) on deletion, which matters for a destructive group operation.

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% and only two parameters exist, both required and documented (event_id with provenance from search_events, group_id as the group UUID). The description adds no format or sourcing detail beyond the schema, so a baseline 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?

The description states a specific verb and resource ('Delete a group') and scopes it to a single event, which separates it from the many other delete_* siblings by resource. It doesn't explicitly distinguish itself from create_group or read_groups, but the destructive action is 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?

The second sentence gives concrete when-not conditions: system groups and groups linked to ticket types, interests, addons, or services cannot be deleted. It stops short of naming an alternative path (e.g., read_groups to verify deletability, or remove_attendees_from_groups for membership cleanup), so the agent must infer next steps.

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