vnc_screenshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says a screenshot is taken and does not state what the output looks like, where the screenshot is returned or saved, whether a live VNC session is required, or any side effects.

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 one front-loaded sentence with no filler or repetition. It communicates the core action immediately and does not waste the agent's attention.

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 tool with one optional, fully documented parameter, this is minimally viable. However, there is no output schema and no statement of the return format, so an agent cannot be certain whether the tool returns an image, a file path, or base64 data.

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 delay parameter is fully documented in the input schema, including units, range, default, and a practical use case. The description itself adds no parameter detail, but with 100% schema coverage, the schema does the heavy lifting and the baseline score of 3 applies.

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 states a clear verb and resource: taking a screenshot of the current screen. It is immediately distinguishable from the sibling VNC input tools, which handle clicks, mouse movement, and key/text entry.

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 tool's purpose is self-evident as the only capture tool among sibling actions, and the delay parameter in the schema adds a clear use case for waiting on processes. There are no explicit exclusions or alternative routing instructions, but none are really needed for this simple, unique-purpose tool.

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