clear_notifications

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

Annotations already signal a mutating, non-idempotent operation, so the description's main added value is the scope: all desktop notifications are affected. This tells the agent the blast radius. It does not disclose whether the clear is permanent, whether it clears only the current user's session, or what happens if there are no notifications, but the annotations lower the bar for additional behavioral disclosure.

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 a single focused sentence with no filler or repetition. It is front-loaded with the verb and resource and every word earns its place. It is an exemplary model of concise tool description.

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 tool with no output schema, the core operation is sufficiently stated. Minor ambiguities remain, such as whether 'desktop notifications' means all operating-system notifications or only notifications from this app, and what the tool returns on success. These are small gaps for such a simple mutation, so the description is nearly complete.

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 zero parameters and schema coverage is 100%, so the schema already fully defines the input surface. The description adds no parameter-level detail, but none is needed. The baseline of 4 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 uses a specific verb, 'Clear,' with a clear resource, 'all desktop notifications.' It unambiguously distinguishes this tool from siblings like send_notification, read_notifications, and list_notifications, which create, read, or list rather than clear. The intent is immediately obvious.

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 no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It does not mention that read_notifications or list_notifications would be better for inspecting notifications first, nor whether clearing only affects this app's notifications or all system notifications. Usage context is only implied by the name and phrasing.

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