Page the user (critical)

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

With no annotations provided, the description carries full disclosure burden. It explains that it bypasses silent/Focus under certain conditions and falls back to time-sensitive delivery, which is key behavioral detail. Missing are aspects like confirmation, side effects, or permissions, but core delivery behavior is transparent.

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 two sentences, no fluff, and immediately conveys purpose, restrictions, and a key behavioral nuance. Every sentence earns its place.

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 simplicity of the tool (3 params, no output schema), the description covers purpose, usage guidance, and a significant behavioral detail. It does not explain return values or side effects, but for a notification tool, these are often implicit. The presence of sibling tools provides context.

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 each parameter has a clear description. The tool description adds little beyond the schema (e.g., 'Short title,' 'urgently' for message). The topic parameter's fallback logic is detailed in the schema, so the description does not significantly enhance semantic meaning.

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 'Send a priority-5 critical page,' using a specific verb and resource. It distinguishes from sibling tools like send_alert by emphasizing urgency and criticality, and explains behavior with Apple's Critical Alerts entitlement.

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 explicitly says 'Use ONLY for things that genuinely cannot wait (production down, urgent approval, safety),' which frames the appropriate context clearly. It lacks explicit mention of when not to use it or alternatives, but the strong 'ONLY' provides effective guidance.

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