capture

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

With no annotations provided, the description must carry the burden. It discloses the output format (PNG), size range, and the prerequisite of an interactive 3D View. It does not mention potential side effects, failure conditions, or whether it is read-only, leaving some behavioral ambiguity.

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 a single, compact sentence that front-loads the output type and size range, followed by the mode and prerequisite. It contains no wasted words or 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?

For a simple tool with two optional parameters and no output schema, the description adequately covers the output (PNG), size range, and the critical prerequisite. It does not explain error handling or what happens if the view is not interactive, but that is a minor gap given the tool's simplicity.

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 schema provides only defaults with 0% coverage, so the description must compensate. It does so by explaining the size range (64..1024) and clarifying that 'view' refers to camera render or viewport, directly enriching both parameters beyond their bare schema definitions.

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 explicitly states the tool captures a PNG preview at sizes 64..1024, either from a camera or viewport, and requires an interactive 3D View. This is a specific verb-resource-output combination that clearly distinguishes it from siblings like inspect or execute.

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?

It clearly communicates a key usage requirement (interactive 3D View) and specifies the two output modes (camera or viewport). However, it does not explicitly contrast with sibling tools or state when not to use it, though the distinct purpose makes the context evident.

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