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

The description adds substantial behavior beyond the annotations: deletion is permanent, cascades to channels and member list, can leave checks alerting nobody, requires the notification_groups:delete permission, counts against a 10-per-minute delete limit, and emails the account owner. These are exactly the side effects and constraints an agent needs before invoking a destructive tool.

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 front-loaded with the core deletion behavior and then efficiently layers cascade effects, safety check, permission, rate limit, and return value. Every sentence adds relevant operational information without filler.

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 this is a destructive, permission-gated, rate-limited operation, the description covers the critical context: what is destroyed, collateral effects, permission requirements, rate limits, and user notification. It also mentions return values, though an output schema exists.

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?

The input schema fully documents the single required id parameter with a clear description and length constraints. The tool description does not add syntax or format guidance beyond the schema, so the baseline score of 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 states a specific verb and resource: permanently delete a notification group, including its channels and member list. This clearly distinguishes it from sibling delete operations such as delete_check and delete_dashboard.

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?

Usage is implied by the destructive nature and permission requirement, but the description does not explicitly say when to use this tool versus alternatives like update_notification_group or assign_notification_group. It gives important operational context but no explicit when-to-use or when-not-to-use guidance.

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