push

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only names the action without mentioning side effects, permissions, delivery semantics, or what happens on failure. For a command that delivers notifications, agents would benefit from knowing if this is a write operation or whether there are prerequisites.

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, focused sentence with no unnecessary words. It is front-loaded and communicates the core purpose effectively without filler.

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?

Despite the tool having 26 parameters and no annotations, the description provides almost no contextual information about platform support, device selection, prerequisites, or command behavior. The existence of an output schema and detailed parameter docs partially compensate, but the description itself is too sparse for such a complex tool.

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 high (92%), so the schema already documents most parameters. The description adds minimal meaning by clarifying that the payload is a push notification payload and the app is the target, but does not significantly enhance understanding beyond the schema.

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 action ('Deliver'), the target resource ('push notification payloads'), and context ('to an installed app'). This distinguishes it from sibling interaction commands like 'press' or 'click' by specifying it concerns push notifications, not UI gestures.

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 is provided about when to use this tool versus alternatives. Given the large sibling list containing similar interaction commands (e.g., 'press', 'send'), it would be valuable to note that this is for push notifications, not UI pushing, but no such differentiation is included.

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