adb_list_permissions

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 explains the tool parses the package dump to show permissions, but does not disclose potential side effects, required permissions, or limitations. The description is accurate for a read-only operation but lacks depth beyond the obvious.

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 only two sentences, front-loaded with the core action and resource, and includes a usage hint. Every sentence conveys essential information without redundancy, making it highly concise and well-structured.

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?

Given the tool's simplicity and lack of output schema, the description adequately conveys the purpose and general output. It specifies that the tool shows install-time and runtime permissions with grant state, which is sufficient for an agent to understand the return value. However, it does not describe the exact format or structure of the output.

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 all parameters documented. The description adds value by explaining that the tool shows install-time and runtime permissions with grant state, which provides context for the filter parameter, but does not add detailed semantics beyond the schema descriptions.

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 lists permissions for a package, specifying both declared and granted, and mentions install-time and runtime permissions with their grant state. It uses a specific verb ('list') and resource package permissions, and hints at its utility in auditing before/after grant/revoke operations, which distinguishes it from siblings like adb_grant_permission or adb_revoke_permission.

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 suggests using the tool for auditing permission state before and after grant/revoke operations, providing direct context. However, it does not explicitly state when not to use it or list alternatives, though the sibling tools suggest similar functionality like adb_permission_audit.

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