render.still

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

No annotations are provided, so the description bears full responsibility. It only reveals that the tool restores prior scene settings after rendering, which is a useful mutation behavior. However, it omits other important behaviors like file overwrite policy, error handling, performance impact, or required scene state. For a writing tool with no annotations, this is insufficient.

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 sentence that is concise and directly states the primary action and a key side effect. It does not waste words. However, given the tool's complexity, it could include a bit more without harming conciseness (e.g., mentioning that it renders the current scene).

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?

With 6 parameters (1 required), no output schema, and no annotations, the description is severely incomplete. It fails to explain the purpose of many parameters (e.g., resolution limits, engine default), output behavior (e.g., file naming, overwriting), or how the tool interacts with the render pipeline. A more complete description would address these gaps.

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 input schema has 0% description coverage (no descriptions beyond titles). The description adds no parameter-level information whatsoever. Parameters like 'camera', 'engine', and 'image_format' require further explanation (e.g., camera object naming, engine trade-offs, format details) but are left entirely to the schema titles and enum values. This fails to compensate for the lack of schema descriptions.

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 action ('render a still image to disk') and the resource ('still image'). The verb+resource combination is specific and distinct from sibling tools like render.settings and render.set_settings. However, it could be more explicit about what exactly is rendered (e.g., 'Renders the current scene as a still image...') to achieve a perfect 5.

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 provides no explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites, whether to use for animation vs stills, or compare to other tools like render.settings. The agent must infer usage solely from the tool name and context.

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