adb_package_info

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

Description indicates a read operation with no side effects, which is appropriate. However, with no annotations provided, it could be more explicit about being non-destructive and requiring device connection.

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?

Single sentence, front-loaded with action, no redundant information. Perfectly concise.

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 info retrieval tool with two parameters and no output schema, the description is sufficient. It covers the key information returned (version, permissions, paths).

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 parameter descriptions 'Package name' and 'Device serial' being self-explanatory. Description adds no extra meaning beyond schema, meeting baseline.

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?

Description clearly states action ('Get'), resource ('installed package'), and specific information retrieved (version, permissions, paths). It distinguishes itself from sibling tools like adb_list_packages which only lists packages.

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?

No explicit guidance on when to use this tool over alternatives. The description implies it's for detailed info, but doesn't contrast with similar tools like adb_list_permissions or adb_file_stat.

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