render_image

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

No annotations are present, so the description carries the burden. It discloses the primary action (render to image file) and the default output path behavior, but does not mention side effects like file overwriting, blocking behavior, or that it uses current render settings.

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?

Two concise sentences with no fluff; the main action is front-loaded and the default path note is directly relevant. Every word earns its place.

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 one-parameter tool with an output schema, the description covers the core behavior and default path. It omits minor details like overwrite semantics or reliance on current render settings, which are arguably implicit but could be more explicit given the lack of annotations.

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 description adds meaning to the filepath parameter by explaining that null/default uses the scene output path. Since schema description coverage is 0%, this compensation is valuable, though it doesn't specify file format or other constraints.

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 'Render the current frame to an image file,' specifying the action and resource. It does not explicitly differentiate from render_animation or render_viewport, but 'current frame' implies single-frame output, making the purpose clear enough.

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 given on when to use render_image versus render_animation or render_viewport, and no alternatives or exclusions are mentioned. The only extra note about the filepath parameter concerns parameter behavior, not tool selection.

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