unity_screenshot_scene

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

The description mentions that the tool 'Returns immediately' (indicating asynchronous behavior) and provides the file path. Since no annotations are given, the description adequately covers behavioral traits like non-blocking operation and return value.

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 extremely concise: two sentences that cover the action, the target, the result, and a key behavioral trait (immediate return). No unnecessary words.

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 lack of output schema and annotations, the description is nearly complete: it explains what the tool does and the outcome. It could mention that the file path is returned, but that is implied. No major gaps.

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?

The input schema already has 100% coverage with descriptions. The tool description adds no extra parameter details, but the schema itself is comprehensive. The description adds overall purpose, which is sufficient.

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 the verb ('Capture'), the resource ('a screenshot of the Scene View camera'), and the result ('Returns immediately with the saved file path'). It distinguishes itself from sibling tools like 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?

The description implies immediate use for capturing the scene view, but does not explicitly state when not to use it or provide alternatives. However, the context of sibling tools (e.g., unity_screenshot_game) makes the distinction clear.

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