render_viewport

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without explaining side effects, whether existing files are overwritten, whether it uses current frame/render settings, or what the return value is. The output schema exists but is not provided in the context, so the description remains the primary source, and it is very thin.

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 one concise sentence that gets to the point without fluff. It is not bloated, and the core purpose is front-loaded. However, it is so sparse that it sacrifices informational completeness, but as a strict conciseness measure, it is efficient.

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 rendering tool, the description is woefully incomplete. It lacks details about file format, naming conventions, whether it respects render settings, how it handles missing cameras, or what the tool returns. With no annotations and only a skeletal parameter schema, an agent cannot confidently predict behavior or integration with other tools.

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 single parameter 'filepath' has no description in the schema (0% coverage) and the tool description does not explain its role, default behavior, or allowed values beyond the schema's type and default null. An agent won't know whether to supply a path or what happens if null is passed, making parameter usage ambiguous.

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 tool renders the viewport (OpenGL) to a file. This is specific about the resource and action. However, it doesn't differentiate from sibling tools like capture_viewport or render_image, which could also capture the viewport, creating potential ambiguity for an agent choosing among them.

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?

There is no guidance on when to use this tool versus alternatives. The description gives no context about use cases, prerequisites (e.g., camera setup, render settings), or when to choose render_viewport over render_image, render_animation, or capture_viewport. An agent is left to infer usage from the name and brief description.

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