get_viewport_screenshot

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

No annotations are provided, so the description carries full burden. It states 'capture a screenshot' but does not disclose whether the tool is read-only, if it modifies the scene, or any side effects. Although a screenshot is typically non-destructive, the description lacks explicit assurance or details on behavior like output format or viewport requirements.

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 concise: one line for purpose, then a bullet list for parameters. Every sentence adds value, and the most important information (what the tool does) is front-loaded. There is no fluff or repetition.

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 tool's simplicity, the description covers the essential aspects: purpose, parameters, and return type ('Image'). It lacks output schema and does not specify image format or resolution details, but for a straightforward screenshot capture, this is largely sufficient. An explicit mention of read-only nature would improve completeness.

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%, so the description must compensate. It explains that max_size is 'Maximum size in pixels for the largest dimension' and user_prompt is for telemetry. This adds meaningful context beyond the schema's type/default, though it could specify units (pixels is clear) or that max_size controls the largest side.

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') and resource ('screenshot of the current Blender 3D viewport'). It is distinct from sibling tools, which focus on asset downloads, code execution, or scene information, making the purpose 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?

While no explicit when-to-use or alternatives are given, the context is clear: it captures a viewport screenshot. Since no sibling tools offer the same functionality, no exclusions are needed. The description implies usage for obtaining a visual representation of the 3D scene.

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