notify

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

The description accurately describes the tool's basic behavior. Annotations already indicate readOnlyHint=false, so no contradiction. However, it does not disclose additional behavioral traits such as permission requirements, blocking behavior, or that it only works on macOS, though the platform is implied in 'macOS'.

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 unnecessary words. It is highly concise and front-loaded with the essential information.

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 simplicity (2 required string parameters, no output schema), the description is reasonably complete. It could mention that it does not return a value or that the notification is non-blocking, but the current level is sufficient for a basic notification tool.

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%, meaning the description should compensate, but it does not describe the parameters at all. The parameter names 'title' and 'message' are self-explanatory, but no additional semantics like character limits or formatting are provided.

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 'Show a macOS notification banner' clearly states the action (show) and resource (notification banner) with platform specificity (macOS). It is distinct from sibling tools like say, set_volume, etc.

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 usage guidelines are provided. The description does not indicate when to use this tool over alternatives like say or other notification-like tools, nor does it mention any prerequisites or exclusions.

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