notify

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds useful context: the notification stays visible for ~6 seconds and displays without opening a window. However, it does not mention return behavior, error handling, or potential blocking, which would be helpful for a complete picture.

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 concise and well-structured: the first sentence states the purpose, the second gives usage context, and the third notes the duration. Every sentence earns its place, with no filler or redundancy.

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 two-parameter notification tool, the description covers purpose, usage, and a key behavioral trait (duration). There is no output schema, so a brief mention of return behavior (e.g., immediate success or void) would improve completeness, but the current level is adequate for most use cases.

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 schema already provides descriptions and examples for both parameters (title and message). The description only says "given title and message" without adding further semantic context, so it does not add value beyond the schema. 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 tool's function with a specific verb and resource: "Show a Windows notification balloon with the given title and message." This is distinct from sibling tools, none of which involve notifications, so there is no ambiguity about what the tool does.

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 provides explicit when-to-use guidance: "Use this tool to notify the user when a long task finishes, when something needs their attention, or to display information without opening a window." It does not mention when-not-to-use or alternative tools, but the use cases are clearly enumerated, making this a strong guideline.

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