adb_notifications

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

No annotations are provided, so the description carries the full burden. It indicates a read-only operation ('Read active notifications') and describes parsing the notification manager dump, implying no destructive side effects. However, it does not disclose potential requirements (e.g., permissions like GET_NOTIFICATIONS) or behavior in edge cases (e.g., no notifications).

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 three sentences: the first states the purpose, the second explains the mechanism, and the third lists use cases. It is front-loaded, concise, and every sentence adds 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?

The description specifies the extracted data fields (package, title, text, etc.), giving a clear picture of the return format without an output schema. It also states the source ('notification manager dump'). Minor gaps: lack of mention of ordering, pagination, or behavior on empty results, but overall sufficient for a simple 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 coverage is 100%, with each parameter described in the schema. The description does not add additional meaning beyond the schema, earning a baseline score of 3.

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 'Read active notifications on the device' and enumerates the extracted fields (package, title, text, importance, channel, flags). It distinguishes itself from sibling tools by focusing on notification state, while siblings like adb_ui_dump or adb_logcat serve different purposes.

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 explicitly lists use cases: 'verifying push notification delivery, monitoring notification state, and testing notification-related features.' This guides when to use the tool, though it lacks explicit exclusions or alternatives, which is acceptable given the specificity.

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