notification_send

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

No annotationsprovided, so description carries full burden. Fails to disclose whether this blocks execution, requires specific OS permissions, handles display duration, or returns success/failure indicators.

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?

Extremely efficient at four words with no redundancy. Front-loaded with the action verb. However, excessive brevity given the lack of schema documentation and annotations leaves it underspecified.

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?

Inadequate for a tool with zero schema descriptions and no annotations. Missing critical context: error conditions, display behavior, permission requirements, and parameter details needed for 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 has 0% description coverage, requiring the description to compensate. Description omits semantics for 'title' and 'body' parameters (length limits, formatting support, required vs optional nature) despite being able to infer basic purpose from the tool name.

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?

Clear verb+resource ('Send a desktop notification') that distinguishes from file and clipboard siblings. However, lacks specificity about the notification mechanism (OS native vs in-app) or target user.

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 on when to use versus alternatives (e.g., when to send a notification vs writing to a log file), prerequisites, or conditions where notifications might fail (permissions disabled, DND mode).

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