parse_screen

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

Discloses side effect of saving an annotated image to a temp file and specifies the backend. However, lacks details on whether the tool is read-only, performance impacts, or prerequisites like instance focus. With no annotations, more context would be beneficial.

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 with no wasted words. The main purpose is front-loaded, and the side effect is clearly stated. Efficient and well-structured.

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?

Output schema exists, so return values need not be described. However, the description fails to cover parameter semantics, and lacks usage guidance. For a moderately complex tool, this is a gap.

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 coverage is 0%, and the description does not explain the parameters 'instance' and 'box_threshold'. Although 'instance' is mentioned briefly, 'box_threshold' is entirely omitted, failing to add meaning beyond the raw schema.

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 it detects on-screen elements (id, type, label, interactive, pixel-center) for a specific instance with backend GLOVEBOX_VISION. It also mentions saving an annotated image, making the purpose unambiguous and distinct from siblings like screenshot or click.

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 tool versus alternatives such as screenshot (for capturing an image) or click_element (for interacting with elements). The description implies detection but does not specify conditions or exclusions.

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