ui_view

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety contract is known. The description adds behavioral detail by noting the screenshot is compressed and returns image content, which is useful for understanding output expectations without overexplaining.

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 11-word sentence that is front-loaded and to the point. No unnecessary words or redundancy.

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?

For a simple read-only tool with one optional parameter and no output schema, the description covers what it returns (image content) and its compression. It lacks explicit details about output encoding or prerequisites (e.g., simulator booted), but these are minor for an agent aware of simulator context.

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 schema provides a full description for the single 'udid' parameter, including a pattern and env var alternative. With 100% schema coverage, the description adds no additional parameter information, which is acceptable but doesn't raise the score above baseline.

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?

Description clearly states the tool retrieves image content of a compressed screenshot for the current simulator view, using a specific verb ('Get') and resource. It distinguishes itself from sibling tools like 'screenshot' by emphasizing 'compressed' and 'image content' rather than a file capture.

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 on when to use this versus sibling tools like screenshot or record_video. The description doesn't mention scenarios or exclusions, leaving the agent to infer usage from context.

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