pushover_send_notification

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It only states 'Send a push notification', omitting details on authentication requirements, side effects, rate limits, delivery guarantees, or error handling. This is wholly inadequate for a 12-parameter tool.

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 a single sentence with no extraneous words, but it is grossly underspecified. Conciseness does not compensate for missing essential information; the description fails to earn its place by providing too little value.

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 tool has 12 parameters, no output schema, and no annotations, the description must provide comprehensive context. It is entirely insufficient, offering no details on return values, error conditions, or usage constraints.

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 only 25% (3 out of 12 parameters have descriptions). The tool description adds no parameter meaning beyond what is in the schema. For parameters like app_token and user_key, the agent has no context on what they represent or how to obtain them.

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 'send' and resource 'push notification via Pushover', making the tool's purpose immediately clear. While it does not explicitly distinguish from sibling tools like pushover_cancel_emergency, the name and description are sufficient given the different actions.

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 (e.g., pushover_cancel_emergency for cancelling). No prerequisites or context provided, leaving the agent without usage boundaries.

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