render-still

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

With no annotations provided, the description carries the burden. It discloses a key behavioral trait: 'restoring prior scene settings after', indicating the tool temporarily changes settings and restores them. However, it doesn't mention whether the image is saved immediately, if the render blocks, or any side effects for unsaved changes.

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 packs essential information: the action, the output, and the restoration behavior. Every word earns its place and there's no fluff.

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 6 parameters, 2 enums, and no output schema, the description is minimal. It covers the primary operation and restoration but misses important context like how the temporary settings interact with the parameters (e.g., engine, resolution) or what success/error responses look like. The complexity is moderate, so a bit more detail would be warranted.

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 is the only source beyond the schema. The description provides no parameter-level explanation; the schema only gives titles ('Destination image path', 'Camera object to use for this render', etc.) without deeper semantics. It doesn't clarify relationships between parameters or usage tips, leaving the agent to infer.

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's action ('Render a still image to disk') and identifies the specific resource (a still image). It distinguishes itself from sibling render-settings/render-set_settings by focusing on the actual rendering operation, but doesn't explicitly name alternatives.

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 implies a use case (rendering a still frame to disk) but doesn't provide explicit when-to-use/when-not-to-use guidance or mention alternative tools like render-settings. No exclusion criteria are given.

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