render_still

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

No annotations are provided, so the description carries the full burden. It mentions rendering to an output path or temp, implying a write operation, but doesn't disclose behavioral traits like required permissions, performance impact, file overwriting, or error handling. It lacks critical context for a mutation tool.

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 extremely concise with a single sentence that front-loads the key action. There is no wasted text, making it efficient and easy to parse.

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 has an output schema, the description doesn't need to explain return values. However, as a mutation tool with no annotations, 0% schema coverage, and two parameters, it lacks completeness. It fails to provide necessary context on what is rendered, usage scenarios, or behavioral details, making it inadequate for safe and effective use.

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 mentions 'output_path' and implies a default to temp, adding some meaning, but doesn't explain the 'format' parameter or its default 'PNG'. It partially addresses one of two parameters, leaving significant gaps.

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 the tool renders a still image, which is a clear purpose, but it doesn't specify what is being rendered (e.g., a scene, viewport, or specific object) or distinguish it from sibling tools like 'get_viewport_screenshot'. It's vague about the resource being rendered.

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?

No guidance is provided on when to use this tool versus alternatives such as 'get_viewport_screenshot' or other rendering-related tools. The description only mentions the action without context or exclusions.

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