blender_capture_viewport

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

With no annotations, the description carries the full burden. It discloses that the operation is 'instantaneous' (non-render) and returns a Base64 PNG. It does not mention potential side effects, but capturing a screenshot is inherently read-only and unlikely to modify the scene. The description adequately conveys its non-destructive nature and output format.

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, efficient sentence that places the primary action first and includes the key output detail. There is no filler or repetition, making it concise and easy to parse.

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 zero parameters, no output schema, and a simple side-effect-free action, the description covers everything an agent needs to know: what it captures, how it returns the result, and the purpose. No missing information affects correct invocation.

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 has zero parameters, so no parameter documentation is required. Per the rubric, a baseline of 4 applies for 0 parameters. The description adds no parameter-specific info, but none is needed.

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 identifies the verb 'captures' and the resource '3D viewport', and specifies the output format (Base64 PNG). This distinguishes it from sibling tools like blender_inspect_scene, which deals with scene data rather than visual captures, and from setup tools that modify state.

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 states the tool is for 'multimodal visual inspection', giving context for when to use it. However, it does not explicitly mention alternatives or when NOT to use it. Given the sibling list includes blender_inspect_scene, a brief exclusion would improve guidance, but the intended use is clear enough.

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