ui_view

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

Annotations already declare readOnlyHint and openWorldHint, so the description does not need to cover safety. However, it mentions 'compressed screenshot' which implies a lossy format but does not specify the output format, resolution, or any side effects, leaving some behavioral gaps.

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?

A single, direct sentence that fully conveys the tool's purpose without any redundant or ambiguous phrasing. Every word 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?

The description lacks information about the output format (e.g., PNG, JPEG, base64), which is critical for an agent to know how to process the result. Since there is no output schema, the description should clarify this. Additionally, it does not differentiate from sibling tools like 'screenshot' in terms of output characteristics.

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 input schema provides a clear description for the only parameter 'udid', and the tool description adds useful context by mentioning the environment variable fallback (IDB_UDID). This adds value beyond the schema alone.

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 specific action ('Get'), the resource ('image content of a compressed screenshot'), and the context ('current simulator view'). It effectively distinguishes this tool from similar siblings like 'screenshot' by emphasizing 'compressed'.

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 explicit guidance on when to use this tool versus alternatives such as 'screenshot' or 'record_video'. The description does not indicate prerequisites, exclusions, or scenarios where this tool is preferred or inappropriate.

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