take_screenshot

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

Annotations mark readOnlyHint=true, and description adds behavioral details: saves to .mcp/screenshots, returns inline image with path/size, preview mode dimensions, timeout behavior, and error conditions. No contradiction.

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?

Single paragraph with clear structure: purpose, mode definitions, behavior, return values, error conditions. Front-loaded with main action. No wasted words.

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 4 parameters, no required ones, and an output schema, the description covers all essential aspects: purpose, modes, return values, save location, timeout, and errors. Output schema exists to detail return fields, so description is complete.

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 already documents all 4 parameters with 100% coverage. Description adds meaning by explaining responseMode options (full, preview, path_only) and their effects, plus preview dimensions, adding 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?

Description clearly states 'Capture a PNG of the running viewport', which is a specific verb+resource. It distinguishes itself from sibling tools (all other tools are about scene editing, project management, etc.) as the only screenshot capture tool.

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 explicit guidance on when to use vs alternatives, but given the sibling list, it's the only screenshot tool, so usage is implied. Lacks explicit 'when not to use' or alternative suggestions.

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