Clear every notification

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's added value is the irreversibility ('no undo'), the permanent/delete-all scope, and the explicit confirmation requirement. These are useful behavioral details beyond the annotations.

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 with no filler: the action comes first, the key caveats follow, and the confirmation requirement is stated plainly. 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 destructive action with two well-documented parameters and no output schema, the description covers what happens, how permanent it is, and what gate must be satisfied. It could be slightly more explicit about the selected account scope and name mark_read/dismiss_notification as alternatives, but the schema and sibling list cover most of that.

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%, so the parameters are already fully documented. The description's 'Needs confirm: true' reinforces the confirm parameter but adds no meaning beyond what the schema already says about confirm, and it says nothing new about account.

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 opens with a specific, unambiguous action: 'Delete all notifications permanently.' It also distinguishes the operation from 'marking them read,' which clearly separates it from sibling tools like mark_read and dismiss_notification.

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 gives clear context: this is a permanent, confirm-gated delete-all operation, and it explicitly says it is not equivalent to marking notifications read. It does not name the alternative tool to use for read-only marking, but the exclusion is enough for an agent to avoid the most likely confusion.

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