unity_graphics_scene_capture

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

Discloses that the output is a base64 PNG that Claude can see directly. No annotations to contradict. Missing details about file size limits or performance impact, but adequate for this 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?

Three concise sentences, each adding value. No fluff. Front-loaded with 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, description explains return type and usage. No need to explain return values further. Sufficient for a capture tool with simple parameters.

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 covers 100% of parameters. The description adds value for the 'port' parameter with usage guidance about parallel-safe routing and referencing unity_select_instance. The width/height parameters are sufficiently described in 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 Scene View as an inline image and returns base64 PNG. Verb+resource is specific, but doesn't differentiate from unity_graphics_game_capture which likely captures the Game View instead.

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?

States 'Use to visually inspect the scene layout' but does not mention when to use alternatives like unity_graphics_game_capture or unity_screenshot_scene. No exclusions or when-not guidance.

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