screenshot-capture

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

With no annotations, the description reveals key behaviors: saves as PNG, returns file path, superSize only applies to Play Mode. It does not mention file overwrite behavior or required permissions, but overall provides sufficient transparency for an AI agent.

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?

Two sentences front-loaded with the action and result. Every word serves a purpose, no fluff.

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 explains the return value (file path). All parameters are described with defaults and constraints. The tool is straightforward and the description covers all necessary aspects.

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 description adds meaningful context beyond the schema: explains tag as optional filename prefix, dimensions as output size, and superSize as supersampling multiplier limited to Play Mode. Schema coverage is 100% but description enriches with practical details.

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 captures a screenshot of Game or Scene view and saves it as PNG. It uses a specific verb 'Capture' and resource 'screenshot', and distinguishes between Play/Edit modes. No sibling tools overlap, so differentiation is implicit.

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 mentions it's useful for visual verification, UI layout, and debugging rendering issues. It provides clear context for when to use but does not explicitly state alternatives or when not to use. However, given no competing sibling, this is adequate.

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