pushover_cancel_emergency

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

No annotations provided. The description mentions canceling 'before it expires' but does not disclose behavior if already expired, side effects, idempotency, or required permissions. For a mutation tool, this is insufficient.

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 short sentence, which is concise but lacks critical information. It is not optimally structured as it omits parameter details and usage context.

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?

With 3 required parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values, error conditions, or prerequisites, leaving significant gaps for the agent.

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 has 3 required parameters (app_token, user_key, receipt) with 0% description coverage. The description adds no explanation of what these parameters are, leaving the agent to guess.

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 the verb 'cancel' and the resource 'outstanding emergency Pushover notification'. It differentiates from sibling tools like pushover_send_notification and pushover_get_receipt by specifying the action on emergency notifications.

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?

No guidance on when to use this tool versus alternatives, such as waiting for expiration or using pushover_get_receipt to check status. The description only states what it does, not when it should be used.

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