pilot_annotated_screenshot

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

Description discloses the screenshot creation with overlays, return format (base64 + file path), and errors. With no annotations, it adequately covers behavioral aspects, though it could explicitly state non-destructive nature.

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?

Well-structured with clear sections: action, usage, parameters, return, errors. Front-loaded purpose. No unnecessary sentences.

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?

Covers prerequisite, errors, return type. Could mention format of base64 output, but sufficient for typical use.

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 single parameter output_path is described in schema (100% coverage). Description adds default behavior (temp directory), providing value beyond 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 the tool takes a PNG screenshot with red overlay boxes and ref labels at element positions. It distinguishes itself from the sibling pilot_screenshot by specifying the debug overlay nature.

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?

Explicitly states when to use (visual debug overlay, verify element positions) and when not to use (for clean capture, use pilot_screenshot). Also mentions prerequisite of pilot_snapshot.

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