get_viewport_screenshot

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

No annotations provided. Description discloses return type (Image) but omits behavioral traits such as whether the viewport must be active, or if it captures overlays. Basic transparency but incomplete.

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?

Description is concise with two focused paragraphs. No extraneous text. However, the default mismatch reduces clarity and could be considered a minor inefficiency.

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?

Parameters and return are covered, but missing details about image format, what 'current viewport' includes (e.g., UI elements), and behavior in multi-viewport setups. Adequate for a simple tool but not comprehensive.

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 has 0% description coverage; description adds meaning for both parameters. However, the default for max_size conflicts with schema (800 vs 1000), causing confusion. user_prompt is explained as telemetry, which is helpful.

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?

Description clearly states the tool captures a screenshot of the current Blender 3D viewport, using specific verb and resource. No sibling tool duplicates this functionality, so differentiation is not required.

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?

Description provides basic usage context (captures current viewport) but lacks guidance on when to use versus alternatives, or prerequisites like viewport visibility. Minimal support for decision-making.

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