render_still

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

Beyond the annotations (readOnlyHint=false, destructiveHint=true), it discloses that rendering blocks 3ds Max and waits, and that the call returns whether the file was actually written. It does not mention potential overwriting of an existing file, but destructiveHint already signals that risk.

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 short and front-loaded, putting the core action first and then the blocking behavior. It is duplicated in Chinese and English, which adds length, but this is reasonable for a bilingual tool and does not obscure the content.

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 only two well-documented optional parameters and no output schema, the description covers the essential call contract: what it renders, where output goes, that it blocks, and what it returns. It could add detail about output format or overwrite behavior, but those are governed by render settings and the destructive annotation.

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?

Both parameters already have full schema descriptions (100% coverage), including the absolute path and the default-frame behavior. The description restates the omit-path behavior rather than adding new semantic detail, so it earns the baseline score of 3.

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?

States a specific action — "Render ... frame to a file" — and the exact resource, plus the return values (resolved output path and whether the file was written). The singular "current (or a named frame)" distinguishes it from multi-frame siblings like render_frames and render_animation.

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 clearly establishes the single-frame use case and that the call blocks until completion, giving an agent a concrete invocation context. It does not explicitly name alternatives or say when not to use it, so it stops short of full routing guidance.

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