adb_ui_dump

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

Describes output structure (coordinates, text, etc.) without annotations. No contradictions. Could mention if hierarchy refresh requires device to be awake, but overall good disclosure.

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?

Two sentences effectively cover purpose and format hints. No redundant information; every sentence earns its place.

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?

Provides sufficient detail on output and formats without an output schema. Could specify prerequisites (e.g., device awake) but overall complete for a UI dump tool.

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?

Adds value beyond 100% schema coverage by explaining format options and their benefits (e.g., 'token-efficient') and clickableOnly purpose. Parameters are well contextualized.

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 'Dump the current UI hierarchy' and specifies parsing into structured element data with coordinates, text, resource IDs, and interaction flags. This distinguishes it from sibling tools like adb_ui_find or adb_tap_element.

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?

Provides explicit guidance on format selection: 'Use format='tsv' for token-efficient compact output, format='xml' for raw uiautomator XML.' However, does not explicitly contrast with alternatives like adb_ui_find for searching rather than dumping.

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