unity_screenshot_game

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

No annotations are provided, so the description carries the full burden. It mentions 'saved on the next frame render', which discloses the async nature. However, it does not mention file size, overwrite behavior, or permissions. It provides basic transparency but lacks depth.

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 very short (two sentences) and front-loaded with the main action. However, the first sentence could be merged with the second, and more detail could be added without losing conciseness. It's efficient but leaves some gaps.

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 (screenshot capture) and the absence of an output schema, the description covers the essential behavior. It lacks details on error handling, file format, or return value, which could be helpful. It's adequate but not comprehensive.

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 coverage is 100%, so baseline is 3. The description adds value by clarifying the default save path and resolution multiplier meanings, and especially emphasizes the 'port' parameter for parallel-safe routing with a strong recommendation. This extra context improves usability.

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 'Capture a screenshot of the Game View', specifying both the action (capture) and the target (Game View). It also notes that the screenshot is saved on the next frame render, adding a timing detail. This is distinct from sibling unity_screenshot_scene, which captures the Scene View, and unity_graphics_game_capture, which may differ in purpose.

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 this tool vs alternatives (e.g., unity_screenshot_scene for scene view, unity_graphics_game_capture for other captures). The description is minimal and does not provide exclusions or prerequisites. However, the sibling list implies differentiation by view type, but this is not stated.

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