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

No readOnly/destructive annotations are present, so the description carries the full burden. It does not disclose how notifications are delivered, whether they are synchronous, if there are rate limits, or any side effects. The poetic language adds no concrete behavioral facts beyond the underlying intent, leaving agents to guess what actually happens.

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 text is short but wastes words on metaphor instead of front-loading the key action. The first sentence, 'Interrupt yourself on your own devices—a phone, a laptop—with the page closed,' is indirect and does not clearly state 'send a notification'. It is not concise in a functional sense because it does not earn its place with actionable 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?

As a send operation with no output schema and no annotations, the description should explain what happens after invocation (confirmation, delivery status, etc.), but it does not. It also fails to clarify whether this is a push notification, an in-app alert, or something else. The agent has insufficient context to fully understand the tool's behavior.

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 100% and each parameter has a clear explanation (e.g., URL destination, short title). The tool description does not add further meaning beyond the schema, so the baseline of 3 is appropriate—the schema already handles parameter semantics.

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 implies notification via 'Interrupt yourself on your own devices', but it never explicitly states 'send a notification' or names the resource (e.g., device, notification). It is not a tautology but remains vague and fails to crisply state the verb and resource, making it hard to distinguish from mail_send or chat_send.

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?

It gives implied usage context: 'For the thing that cannot wait until the next time somebody looks' suggests urgency, and 'An answer to a question belongs in the thread it was asked in, not here' offers a when-not. However, it never mentions alternative tools (e.g., chat_send, mail_send) or explicit conditions, leaving the guidance implicit.

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