dismiss_all_notifications

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

Annotations already mark the tool destructive, but the description adds important behavior: notifications are permanently deleted, cannot be undone, and all notifications for the current user are affected. This goes beyond the annotation and helps agents warn users.

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 short, front-loaded with the main action and scope, and contains only necessary warnings and return information. Every sentence 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?

For a zero-parameter destructive tool with an output schema, the description provides all essential context: scope, irreversibility, a pre-check recommendation, and expected return. Nothing important 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 are no parameters, so the description does not need to explain parameter semantics. The baseline for a zero-parameter tool is 4, and the description is complete in that regard.

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 names a specific verb ('Dismiss'), clarifies it as permanent deletion of ALL notifications, and scopes it to the current user. This clearly distinguishes it from the sibling dismiss_notification tool.

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?

It gives clear guidance to use list_notifications first to review what will be dismissed. It does not explicitly mention using dismiss_notification for individual notifications, but the 'ALL' scope and zero parameters make the appropriate use case clear.

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