get_viewport_screenshot

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states only the action and does not mention whether the screenshot is returned directly, saved to disk, or how max_size affects the output. This is a significant gap since there is also no output schema.

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 direct sentence with no filler. The action and resource are front-loaded, and every word earns its place.

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 read-only screenshot tool, the description covers the core action and the schema covers the only parameter. However, the absence of an output schema or annotations leaves the return format and side-effect profile under-specified. A brief note about what the agent receives would make it complete.

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 sole parameter, max_size, is fully documented in the input schema with type and default. Since schema description coverage is 100%, the description does not need to repeat parameter details; however, it also adds no extra nuance about how max_size influences the screenshot.

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 uses a specific verb, 'Capture', and a clear resource, 'screenshot of the current Blender 3D viewport'. It clearly distinguishes this tool from all listed siblings, none of which perform screenshot capture.

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 context is clear: this tool is for capturing the current Blender viewport, and there is no competing screenshot tool among the siblings. It does not state explicit when-not conditions, but the practical usage is obvious from the description.

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