dismiss_notifications

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

Despite lacking annotations, the description honestly discloses that the tool's effectiveness is uncertain and that the underlying call may do nothing. This provides important behavioral context, although it does not fully explain what happens when it works.

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 overly verbose, containing long explanations about unverifiability and fallback issues. It could be concise by simply stating the purpose and a brief caveat; the current length wastes words and reduces clarity.

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 no parameters and no output schema, the description should explain what 'dismiss' entails (e.g., what happens to notifications). It only focuses on doubt and does not provide sufficient context for reliable use.

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?

With zero parameters and 100% schema coverage, the description does not need to add parameter information. The baseline for zero-parameter tools is 4, and the description does not detract from this.

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 explicitly states 'Dismiss all currently visible Hyprland built-in on-screen notifications,' providing a specific verb and resource. However, it immediately undermines this clarity by casting doubt on its functionality, which could confuse an agent.

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 offers no guidance on when to use this tool versus alternatives like close_window or any other. It only discusses the tool's unreliability and does not help the agent decide when this tool is appropriate.

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