Delete Notification

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

With no annotations, the description carries the full burden of disclosing behavior. It states 'permanently deletes' (irreversible) and that monitors will stop sending alerts, revealing a side effect. However, it does not mention any error conditions or prerequisites beyond the operation itself, so it is not fully exhaustive.

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 concise and well-structured, consisting of two clear sentences. It avoids unnecessary detail and gets straight to the point, making it easy for an agent to parse and understand the tool's primary function.

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 the tool's simplicity, the description provides adequate context: it defines the action (permanent deletion) and the immediate impact (monitors stop using the channel). It does not explain return values or error handling, but since an output schema is present, that information may be covered elsewhere. The description is sufficiently complete for its complexity.

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 has a single parameter with a clear description, and the schema coverage is 100%. The tool description itself does not add additional insight about the parameter beyond what the schema already provides, so it meets the baseline for high schema coverage.

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 that the tool permanently deletes a notification channel. It also explains the consequence (monitors using it will no longer send alerts), which makes the purpose unambiguous. It distinguishes itself from sibling tools by specifying 'notification channel' rather than generic deletion.

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 explains what the tool does and its effect, but does not explicitly state when to use it or provide alternatives. It lacks guidance on scenarios like 'use this when a notification channel is no longer needed' or comparison with other delete tools. This is a clear but minimal usage description.

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