Show desktop notification

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

With no annotations provided, the description carries the full burden and does supply some useful context: the notification is 'native' and limited to Windows or macOS, implying platform-specific behavior. It does not disclose side effects, permissions, failure modes, or whether the call blocks, but the core behavior is accurately and plainly 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 concise sentence with no filler, and the key behavior is front-loaded. It is appropriately sized for a simple tool, though the brevity contributes to missing usage and parameter details.

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 annotations, no output schema, and zero parameter descriptions, the definition is not complete enough. It lacks guidance on choosing this tool over the generic 'notify' sibling, does not explain the optional 'subtitle' parameter, and provides no context about expected behavior or platform limitations beyond the OS mention.

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 0%, and the description adds no explicit parameter-level meaning. The parameter names 'title' and 'message' are fairly self-explanatory in the context of a desktop notification, but 'subtitle' remains ambiguous, and the description does not clarify how it is used on Windows versus macOS. Some indirect value comes from the domain framing, but it does not compensate for the fully undocumented schema.

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 and resource: 'Show a native Windows or macOS desktop notification.' It clearly identifies what the tool does and is naturally differentiated from the audio-focused siblings by the word 'desktop.' However, it does not explicitly distinguish itself from the generic 'notify' sibling, so it falls just short of a 5.

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?

No guidance is given about when to use this tool versus alternatives. The description does not mention the generic 'notify' sibling or the audio notification tools, nor does it state any exclusions or preferred use cases. An agent would have to infer the selection criteria from the tool name and sibling list.

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