unity_graphics_game_capture

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

Discloses output format (base64 PNG), that Claude can see it directly, and that it captures the Game View camera. No side effects or permissions mentioned, but given no annotations, this is adequate transparency.

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 concise sentences: first states action and output, second gives use case. No extraneous information, front-loaded with the essential purpose.

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 adequately explains the return value (base64 PNG). Input is fully covered by schema. The tool is simple, so this is sufficient.

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 describes all 4 parameters with coverage 100%. The description adds extra guidance for the port parameter ('Always include it when multiple instances run') and implies default values for width, height, and cameraName, which adds value 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?

Clearly states it captures the Game View camera and returns a base64 PNG that can be displayed inline. It distinguishes from scene capture (sibling unity_graphics_scene_capture) by specifying 'Game View', but does not explicitly differentiate from unity_screenshot_game which may have similar 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?

Provides the use case 'Use to see what the player sees.' This gives clear context but does not specify when not to use or compare to 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.