android_notifications

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds useful behavioral context beyond those: it requires prior user grant of notification access and warns that notification text is untrusted data. There is no contradiction with the annotations.

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 two tight sentences. The main action and scope are front-loaded, and the security warning about untrusted notification text is a concise, valuable addition with no wasted words.

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 read-only list with one optional parameter, the description covers the key operational facts: permission prerequisite and untrusted data. It does not describe the return shape, but with no output schema and the verb 'list,' the returned data type is reasonably inferable.

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 fully constrains the single 'limit' parameter with type, default, minimum, and maximum, but provides no description. The tool description does not mention 'limit' at all or explain how it affects results, so with 0% schema description coverage the description fails to compensate for this 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 starts with the specific verb 'List' and the resource 'active notifications,' which clearly states what the tool does. It also distinguishes itself from sibling tools like android_notification_open, android_notification_dismiss, and android_notification_reply by focusing on listing rather than acting on 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 provides a clear precondition: use after the user grants Android notification access. It does not explicitly name alternatives or exclusions, but the sibling tool names make the read-only listing vs. action distinction reasonably obvious.

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