get_viewport_screenshot

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

With no annotations, the description must disclose behavioral details. It only states the action without explaining whether the screenshot saves to a file, returns image data, or has side effects. The optional 'filepath' parameter hints at saving, but its behavior is unexplained, leaving the agent unaware of the tool's actual behavior.

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 fluff. It is well-structured and front-loaded, focusing on the core action without unnecessary details.

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?

The tool has one optional parameter and an output schema, but the description does not explain what happens with the screenshot or what the output contains. The filepath parameter is undocumented, and there is no mention of return values or side effects. This is inadequate for an agent to call it correctly.

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 explain parameter semantics. The single parameter 'filepath' is not mentioned at all. The agent cannot infer whether it is a destination path, source path, or what the default null means. This is a critical omission for correct invocation.

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 states a clear verb ('capture') applied to a specific resource ('screenshot of the active 3D viewport'). It is distinct from sibling tools like render_image and render_turntable, indicating exactly what operation is performed.

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 description clearly implies when to use it: to capture the current 3D viewport. However, it does not explicitly state when not to use it or mention alternatives (e.g., render_image for offline rendering), leaving some inference required.

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