list_notifications

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals the underlying 'dumpsys notification' mechanism and notes it is a summary, but it does not explain whether the operation is read-only, requires permissions, or has any side effects on the device or notification state.

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 filler, and it front-loads the core purpose. It is appropriately concise, though it sacrifices needed detail about usage and the serial parameter.

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?

The tool is simple and has an output schema, but the description is incomplete for correct invocation: it lacks parameter guidance, usage alternatives, and behavioral safety context. An agent cannot fully determine when or how to use the optional serial parameter.

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?

The schema has zero description coverage and the only parameter, 'serial', is not mentioned or explained in the description. Since the description must compensate for the lack of schema documentation, the complete absence of parameter semantics is a severe gap.

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 summarizes currently active notifications on the device and even identifies the underlying source as 'dumpsys notification'. It is specific about the resource and scope, though it does not explicitly differentiate itself from sibling tools like open_notification_panel.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The phrase 'currently active notifications' only implies a narrow use case, leaving the agent to infer when this should be called.

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