unity_screenshot_scene

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

The description states it returns immediately with the saved file path, which discloses the return value and non-blocking behavior. However, it does not mention file format, overwrite behavior, or error cases. With no annotations, more detail would improve 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 sentences with no fluff. The key action and return behavior are front-loaded. Every word serves a 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 (saved file path). Parameters are documented in the schema. However, missing details like file format, overwrite policy, or permissions reduce completeness slightly.

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?

Input schema covers all 4 parameters with descriptions, so baseline is 3. The description does not add additional context beyond the schema, such as typical use cases for width/height or the importance of port for parallel routing.

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 Scene View camera', specifying the exact resource (Scene View) and action (screenshot). This distinguishes it from sibling unity_screenshot_game which captures the Game 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?

No guidance is provided on when to use this tool versus alternatives. For example, it does not mention that unity_screenshot_game should be used for capturing the Game view, or any prerequisites like ensuring the scene view is active.

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