Dismiss matching Omarchy notifications

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

With no annotations, the description carries the full behavioral burden. It discloses the 'visible' scope and substring matching, but does not specify whether all matching notifications are dismissed, whether case-sensitivity applies (only in schema), or any side effects. The operation implies destructive action, but this is not explicitly stated.

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 sentence with no waste. The core action and condition are front-loaded, making it immediately understandable.

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 simple tool with one parameter and no output schema, the description is largely sufficient. It covers the operation and its condition. Minor gaps (e.g., whether all matches are dismissed, case-sensitivity only in schema) exist but do not seriously impede correct invocation.

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 coverage is 100%, and the parameter description ('Case-sensitive headline substring') already provides the meaning. The tool description's reference to 'supplied substring' adds no additional semantic value beyond what the schema offers. Baseline 3 is appropriate.

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 action (dismiss), the target (visible notifications), and the matching condition (headline contains substring). It is specific and distinguishes from sibling notification tools like notification_send, notification_time, and notification_dnd_set, which operate on different aspects.

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 implies its usage context by restricting to 'visible notifications' and matching on headline, which sets clear conditions for invocation. However, it does not explicitly mention when to prefer this over other notification tools, though the intent is fairly obvious from the action. It lacks explicit exclusions or alternatives.

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