Send push notification

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explains the subscription input format well, but says nothing about the required preconditions (VAPID keys configured, subscription validity), delivery semantics, failure behavior, or whether notifications are queued or fire-and-forget. For a network-side-effecting tool with zero annotation coverage, this is a significant gap.

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?

One efficient sentence that front-loads the core purpose before the parenthetical format detail. No redundant filler, though the parenthetical is slightly convoluted (three nested clauses). It earns its place by clarifying the crucial subscription input contract.

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?

Web Push is a protocol-heavy operation with dependencies — VAPID key generation (push_generate_keys), env configuration (set_env), and app existence (create_app) — none of which are hinted at. There is no output schema and no annotations, so the description is the only guide, and it omits these prerequisites. Incomplete for a tool with this much hidden setup.

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 only 25% (only 'subscription' has a schema description), so the description must compensate. It does add clear meaning for 'subscription' by specifying the exact source format (PushSubscription.toJSON()), which goes beyond the schema. However, 'app' is left undefined — an agent cannot tell whether it's a name, ID, or identifier from create_app — and 'title'/'body' rely on common sense. Partial compensation only.

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 states a specific verb ('Send') and a precise resource ('Web Push notification to a browser subscription'), which clearly differentiates it from sibling send_email. The explicit reference to Web Push and browser subscriptions leaves no ambiguity about what the tool does, and it stands apart from push_generate_keys by being the send-side counterpart.

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 gives implied workflow context — that the frontend supplies a PushSubscription.toJSON() payload — but never explicitly states when to use this tool vs. alternatives. It notably fails to mention the prerequisite relationship with push_generate_keys (VAPID keys must exist) or that the app must be pre-created via create_app. No when-not-to-use guidance is provided.

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