unity_screenshot_game

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

The note 'saved on the next frame render' reveals a timing detail, but with no annotations, the description lacks disclosure on behavioral aspects such as file overwrite policy, required permissions, or whether the tool blocks execution. This is mediocre transparency for a capture tool.

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 concise, consisting of only two sentences with no redundancy. The first sentence front-loads the primary action and resource, making it immediately scannable and informative.

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 the tool's simplicity (no output schema, 3 well-documented params), the description covers the essential purpose and a key behavioral aspect (timing). It could mention file format or overwrite behavior, but it is largely complete for an agent to understand and invoke the tool.

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?

All three parameters (path, port, superSize) are already described in the input schema with clear defaults and context (e.g., port references unity_select_instance). The description adds no extra meaning beyond what the schema provides, so baseline 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 clearly states the tool captures a screenshot of the Game View, a specific resource. It distinguishes from sibling tools like unity_screenshot_scene and unity_screenshot_editor_window by specifying 'Game View', making the purpose unambiguous.

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 provides no guidance on when to use this tool over alternatives like unity_screenshot_scene or unity_graphics_game_capture. It does not mention prerequisites, exclusions, or context where this tool is preferred.

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