Generate Web Push keys

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals idempotency ('or return existing') and a security property ('private key never leaves this machine'), which go beyond the surface operation. However, it doesn't mention error scenarios or dependencies (e.g., whether the app must already exist), so it falls short of comprehensive transparency.

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, front-loaded with the primary action and includes only essential details. No wasted words, and the security note is placed at the end without bloating the entry.

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?

The description covers the tool's purpose, idempotency, output, and a security aspect, which is decent for a simple tool. However, the unexplained 'app' parameter is a significant omission, and there is no mention of errors or prerequisites. Overall, it's adequate but not fully self-sufficient.

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 0% and the description does not mention the 'app' parameter at all. An agent cannot infer what value to pass (app ID, name, etc.) from the description. Since the schema provides no guidance either, this is a major gap.

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 ('Generate') and resource ('VAPID keys for Web Push'), and clarifies that it returns an existing set if present. This clearly distinguishes it from siblings like 'push_send' (sending) and 'create_app' (app creation). The purpose is unambiguous and not a tautology.

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 provides clear usage context: it returns the public key for pushManager.subscribe() in the frontend, implying it should be called when setting up push notifications. It doesn't explicitly mention alternatives or when not to use it, but the context is sufficient for an agent to select it appropriately among the listed siblings.

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