ui_dump

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

The readOnlyHint annotation already covers the safety profile (read-only operation), and the description adds scope ('selected device') and a processing detail ('normalize'). However, it does not explain what normalization entails, possible side effects (e.g., blocking on UI response), or error behavior. The description adds some but not rich behavioral context.

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, tightly worded sentence: 'Capture and normalize the selected device UIAutomator hierarchy.' It front-loads the primary verb and object, with no wasted words or redundant phrases.

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?

With no output schema and no parameter explanation, the description is insufficient for full comprehension. It does not state what the tool returns (presumably the hierarchy) or elaborate on the 'normalize' step. The tool is simple, but the lack of return-value and parameter details leaves gaps for an agent to guess.

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 only parameter, 'compact', has zero description coverage in the schema and is not mentioned in the tool description. The agent cannot determine what 'compact' does, making the parameter's semantics completely opaque. This is a critical gap for a documented optional parameter.

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 captures and normalizes the UIAutomator hierarchy for the selected device. This specific verb+resource combination distinguishes it from sibling tools like screen_capture (image capture) and ui_find (searching UI), making its purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., device must be selected via device_select), or scenarios where ui_dump is preferable to ui_find or screen_capture. The agent must infer usage from the name alone.

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