send_notification

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world operation, so the description is not contradicting anything, but it adds no behavioral context of its own. It says nothing about whether the notification is logged to history, how 'critical' urgency behaves (persistence, override of DND), or delivery failure modes — all relevant given the sibling notification tools.

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?

A single front-loaded sentence with no filler and the resource stated first. It is efficient, though it spends most of its words duplicating schema field names.

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 four-parameter tool with full schema coverage and annotations covering the mutation profile, the description is minimally sufficient. It could have been complete by noting history/DND interaction, which is the one thing an agent cannot derive from the structured fields.

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%, so all four parameters including the urgency enum are already documented in the input schema. The description merely restates the field names without adding format, defaults, or semantics beyond what the schema provides, which is the baseline case.

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 names a specific verb (Send) and resource (desktop notification) plus the data it carries, so an agent can immediately tell it apart from the notification-management siblings (list_notification_history, close_all_notifications, toggle_dnd). It stops short of explicitly naming those siblings as alternatives.

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?

There is no guidance on when to send a notification versus using other channels like set_timer or projector_speak, and no note about interaction with DND/paused-notification siblings. The agent must infer usage entirely from the verb.

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