send_push_notification

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

Annotations already indicate destructive write (readOnlyHint=false, destructiveHint=true). Description adds only a **[Write]** tag, providing no further behavioral details like permission requirements or delivery guarantees.

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?

Extremely concise at one sentence plus a tag. No wasted words, but lacks structure (e.g., separate sections for behavior, usage). Appropriate for simple tool but could benefit from more detail.

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?

For a destructive tool with 5 parameters, the description omits important context like return value (confirmation?), error cases, and idempotency implications. Given no output schema, this gap is significant.

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%, so the schema already describes parameters. The description does not add additional meaning beyond what's in the parameter descriptions.

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?

Clearly states it sends a push notification to mobile app users. The **[Write]** tag reinforces the action type. While it distinguishes from siblings via specific tool name, it lacks details on scope (e.g., which mobile apps).

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 vs alternatives like `send_emergency_broadcast` or `schedule_notification`. No prerequisites or context provided.

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