Capture a high-resolution screenshot of the active screen to provide visual context for desktop control and automation tasks.
Capture a high-resolution screenshot snapshot of the active screen and windows.
| Name | Required | Description | Default |
|---|---|---|---|
| purpose | No | Optional reason for capturing screen. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full burden. It states the capture scope ('active screen and windows') but does not disclose whether the tool returns an image, saves a file, requires a display, or behaves differently in headless environments.
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, front-loaded sentence with no filler. 'Screenshot snapshot' is slightly redundant, but overall it is appropriately concise.
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 no output schema and no annotations, the definition leaves a significant gap: it does not say what the agent receives after capture (image data, file path, etc.) or what prerequisites exist. Purpose is clear, but the operational result is unknowable.
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 only parameter, 'purpose', is fully described in the schema as 'Optional reason for capturing screen.' With 100% schema coverage, the description does not need to compensate, and adding no param-specific detail is acceptable.
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 uses a specific verb ('capture') and a clear resource: a high-resolution screenshot of the active screen and windows. It is immediately distinct from the listed sibling tools, none of which perform screen capture.
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 given about when to use this tool versus alternatives, and no alternative capture tool is referenced. An agent cannot infer selection criteria from the description or the sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.