viewport_screenshot

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

No annotations present, so description carries full burden. It only states the action and requirement. It does not disclose whether the operation is destructive, overwrites existing files, what file format is used, or any side effects. Lacks transparency on behavior beyond the basic action.

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 extraneous information. The first sentence immediately states the purpose, and the second provides a critical prerequisite. Every sentence is earned.

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 one optional parameter and no output schema, the description is adequate but incomplete. It does not explain what the output file is (image), where it is saved, or what format. The prerequisite is mentioned. Could be more complete by clarifying the output and any side effects.

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 description coverage is 0%, and the description does not mention the 'output' parameter at all. The parameter is simple (string with default), but the description should explain that it controls the filename of the captured screenshot. This is a missed opportunity to add value beyond the 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 the verb 'capture' and the resource 'live Blender window's 3D viewport'. Distinguishes from sibling tools like render (which produces a rendered output) and view_image (which views an existing image). Purpose is unambiguous.

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?

Specifies the prerequisite (MCP Bridge addon running in an open Blender session), which is helpful context. However, it does not provide guidance on when to use this tool versus alternatives like render or view_image. No explicit exclusions or when-not-to-use guidance.

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