adb_package_info

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

The description lists the categories of information returned (version, permissions, paths), which gives a reasonable overview of behavior. However, since there are no annotations, it should also disclose potential side effects (none expected), authentication needs (none), or any other operational context, which is absent.

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, front-loaded sentence of 9 words. It efficiently conveys the core purpose and output categories 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 information retrieval tool, the description is reasonably complete. It mentions the key output categories, though it could further clarify that the tool operates on installed packages and suggest using adb_list_packages for discovery. No output schema exists, so the description partially compensates by listing return categories.

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%, so the description adds no additional meaning beyond what the schema already provides. The parameter descriptions in the schema are clear, and the tool description is concise but does not elaborate beyond the schema's existing explanations.

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 retrieves 'detailed info' about a package, including specific attributes like version, permissions, and paths. This distinguishes it from sibling tools such as adb_list_packages (which only lists names) and adb_list_permissions (which only lists permissions).

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 no guidance on when to use this tool versus alternatives. For example, it does not mention that adb_list_packages should be used to discover available packages first, nor does it indicate any prerequisites like requiring package installation.

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