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

With no annotations provided, the description carries the full burden. The first word 'Read' clearly signals a read-only operation, and the mention of returning a structured list discloses the expected output. It does not cover edge behaviors like notification permissions or empty states, but for a simple status tool the core behavior is transparent.

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 sentence, front-loaded with the action ('Read'), and contains no filler. Every word contributes: platform (Android), scope (current notifications), and return format (app, title, text).

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 simple one-parameter tool with no output schema, the description adequately explains what it returns. It could mention caveats like notification permission requirements or that 'active' excludes history, but the current text provides enough context for an agent to invoke it correctly.

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 100% – the udid parameter is already documented as 'Device serial number (UDID)'. The tool description adds no additional parameter-level meaning, so the baseline of 3 applies: the schema does the heavy lifting.

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 states a specific verb ('Read') and resource ('current notifications on an Android device'), and defines the return shape ('structured list of active notifications (app, title, text)'). This clearly distinguishes it from the iOS counterpart (ios_notifications_capture) and other device_* tools without needing to open schemas.

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 gives clear context for when to use the tool: when reading current Android notifications is needed. However, it does not explicitly mention alternatives or exclusions (e.g., 'for iOS use ios_notifications_capture'), so the guidance remains implied rather than explicit.

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