get_ui_tree

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

No annotations exist. The description implies a read operation but does not disclose potential side effects, performance impacts (though maxDepth/maxNodes hint at risks), or required permissions. For an unannotated tool, more transparency is needed.

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 concise sentence, which is efficient but omits critical information about parameters and usage. It achieves brevity at the expense of completeness.

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 three parameters with 0% schema coverage, no output schema, and no annotations, the description fails to provide adequate context. It does not explain return value, parameter constraints, or when to apply maxDepth/maxNodes.

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 0%, and the description does not explain any of the three parameters ('sessionId', 'maxDepth', 'maxNodes'). The schema provides no meaning beyond types and constraints.

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 verb ('read'), the resource ('accessibility hierarchy'), and the platforms ('Android UIAutomator or iOS WDA'). It effectively distinguishes from siblings like 'get_visible_elements' or 'take_screenshot'.

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 the 21 sibling tools (e.g., 'get_visible_elements'). The description does not mention context, prerequisites, or excluded scenarios.

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