delete_notification

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

No annotations are provided, so the description carries the full burden. It discloses that this is a destructive operation ('Delete all gateway notifications') and specifies the target ('error messages or warnings'), but it does not mention potential side effects, permissions required, or confirmation prompts. The description adds some behavioral context but lacks completeness for a mutation 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 two concise sentences with zero waste. The first sentence states the action and resource, and the second provides usage guidance, making it front-loaded and efficiently structured.

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 complexity (a mutation with 0 parameters, no output schema, and no annotations), the description is reasonably complete. It explains what the tool does and when to use it, but it could benefit from additional details on behavioral aspects like irreversible effects or error handling, which are not covered by other structured fields.

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 0 parameters with 100% coverage, so no parameter documentation is needed. The description does not add parameter details beyond the schema, but since there are no parameters, a baseline of 4 is appropriate as it does not need to compensate for any gaps.

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 the specific action ('Delete all gateway notifications') and the resource ('gateway notifications'), distinguishing it from siblings like 'reboot_gateway' or 'get_devices'. It also specifies the purpose ('clear error messages or warnings'), making the verb+resource combination precise and unambiguous.

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 explicitly states when to use this tool: 'Use this to clear error messages or warnings from the Plugwise gateway.' This provides clear context for its application, distinguishing it from other tools that might manage devices or settings rather than notifications.

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