desktop_screenshot

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

With no annotations, the description carries full burden. It discloses the tool captures a JPEG screenshot of the XFCE desktop, but does not state whether it captures the full screen or active window, if any prerequisites exist (e.g., desktop must be running), or if there are side effects. Adequate but gappy.

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 sentence with no wasted words, efficiently conveying the core purpose and the return type.

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?

Given no output schema, the description is vague about the return format ('image content' – base64? URL?). It also lacks information about prerequisites, typical use with other desktop tools, and the sandbox context. For a tool with 3 parameters and no output schema, more completeness is needed.

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 description coverage is 67% (id parameter has no description). The tool's description does not add meaning beyond the schema: it does not explain what 'id' refers to (likely sandbox ID), nor provides additional context for 'quality' or 'max_width' parameters. Parameters are not mentioned in the description.

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 JPEG screenshot of the sandbox desktop and returns it as image content. It specifies verb, resource, format, and environment, distinguishing it from sibling tools like browser_snapshot and desktop interaction tools.

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?

The description implies usage when a screenshot of the sandbox desktop is needed, but provides no explicit guidance on when to use this versus alternatives like browser_snapshot, nor any exclusion criteria.

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