create_push_notification

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

The description discloses that the tool creates a record (push notification) and returns a deploy-ready payload. It also mentions token support in title and body. With no annotations provided, this covers key behavioral aspects, though it lacks details on required permissions or side effects.

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 concise with three sentences: purpose, return value, and additional detail about tokens. No unnecessary words or repetition. Well-structured and front-loaded.

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 complexity (6 parameters, no output schema, no annotations), the description provides a clear purpose, return value, and token support. It is fairly complete, though it could mention prerequisites or the effect of the 'condition' parameter more explicitly.

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 83%, with most parameters having descriptions. The description adds context about ${field} tokens in title and body, which supplements the schema. However, it does not add meaning to parameters like 'condition' or 'route_to' beyond what the schema already provides.

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 tool creates a ServiceNow push notification for the Now Mobile app. It mentions the return value (deploy-ready payload for sys_push_message table), but does not explicitly distinguish from the sibling 'create_notification' which likely handles email 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?

The description implies the tool is for mobile app notifications by stating 'for the Now Mobile app', but it does not explicitly state when to use it versus alternatives like 'create_notification'. No exclusions or prerequisites are mentioned.

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