adb_dumpsys

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

No annotations are provided, so the description must compensate. It only states the basic action without disclosing behavioral traits like potential output size, performance impact, or that dumpsys is generally read-only. The agent lacks transparency on what happens when running the command.

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 concise with two sentences and no fluff. It front-loads the primary purpose and includes a key tip. However, it could benefit from a brief mention of output format or typical use cases without losing conciseness.

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 no output schema, the description fails to explain what the tool returns (likely text). It also lacks context among many sibling tools, such as when to use dumpsys over other info-gathering tools. The parameter descriptions are complete, but overall context is insufficient.

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 baseline is 3. The description adds minimal value by reiterating the 'list' usage, but it does not explain the other parameters (args, device, result_handle, result_handle_ttl) beyond what the schema already provides.

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 runs dumpsys for a specific service, with a verb ('run') and resource ('dumpsys for a service'). It distinguishes from siblings by being the dedicated dumpsys tool, though it could be more specific about the purpose (dumping system service state).

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 guideline: using 'list' to see all services. However, it does not discuss when to use this tool versus siblings like adb_battery or adb_device_info, nor does it mention prerequisites or alternatives.

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