unity_graphics_game_capture

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

With no annotations provided, the description partially carries the burden. It mentions the output is a base64 PNG and that it captures the Game View camera, but does not disclose potential side effects, performance implications, or whether the game must be running.

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 three sentences, front-loading the primary purpose. Every sentence adds value without redundancy.

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 moderate complexity (4 parameters, no output schema), the description provides essential purpose and parameter guidance. However, it could mention return format details like the fact that the image is base64-encoded and that it returns a data URI or similar.

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%, but the description adds value by explaining that the 'port' parameter is for parallel-safe routing and should be obtained from 'unity_select_instance'. This adds meaning beyond the 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?

The description clearly states it captures the Game View camera as an inline image and returns a base64 PNG that Claude can see directly, distinguishing it from sibling tool 'unity_graphics_scene_capture' which likely captures the Scene View.

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 says 'Use to see what the player sees,' providing clear context for when to use this tool. However, it does not explicitly mention when not to use it or suggest alternatives like 'unity_screenshot_game' or 'unity_graphics_scene_capture'.

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