adb_dumpsys

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

No annotations are provided, so the description bears the full burden of disclosing behavioral traits. It only states the action, without mentioning potential performance impacts, output format, or side effects of running dumpsys. This is insufficient for a tool that may produce verbose output or affect system load.

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 extremely concise, consisting of two short sentences with no redundant information. It is front-loaded with the core purpose, making it quick to parse and understand.

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 lack of an output schema and annotations, the description is minimally adequate. It covers the main function and a key parameter insight, but it omits details about the output format, typical verbosity, or behavioral notes, leaving gaps for an agent to fully understand the tool's effects.

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 description adds semantic value beyond the input schema by noting that using 'list' as the service parameter lists all available services. This helps the agent understand a special usage mode not evident from the schema alone, improving parameter interpretation.

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 action ('Run dumpsys') and the target ('for a specific service'), making it easy to understand the tool's purpose. It distinguishes from sibling tools by specifying that it operates on a particular service, which sets it apart from more general or specific adb tools.

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 implies usage for inspecting system services and mentions using 'list' to discover services, but it does not provide explicit guidance on when to use this tool versus alternatives or when not to use it. The context is sufficient for basic use but lacks comparative guidance.

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