screenshot

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely says 'Capture screenshot' without mentioning whether the operation is read-only, what platform or device it targets, or any side effects. This is a minimal disclosure that fails to explain what happens or what constraints exist.

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 very concise (one short sentence), but it is under-specified for a tool with a parameter and sibling alternatives. While there is no waste, it is not appropriately sized because it lacks necessary context, making it more of an under-specification than a well-structured concise description.

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 tool is simple, and the schema covers the parameter, but the description omits critical context such as the target environment (simulator/device), how it differs from sim_screenshot_hires, and what the screenshot contains. Given the sibling tools, this context is essential for proper selection and 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 input schema already provides 100% coverage for the single parameter, including an enum and description of 'returnFormat.' The description adds no extra semantic value, so the baseline of 3 is appropriate.

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 action: 'Capture screenshot.' It uses a specific verb and resource, so the basic purpose is clear. However, it does not differentiate from the sibling tool 'sim_screenshot_hires,' which also captures screenshots but in a specific context, so it lacks sibling differentiation.

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 alternatives like sim_screenshot_hires or snapshot_ui. There is no mention of intended scenarios, prerequisites, or exclusions, leaving usage entirely implicit.

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