render_set_frame_range

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the mutation behavior is known. The description adds that this operation sets render frame range but does not disclose side effects such as overwriting previous settings or whether any render setup is required.

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 Chinese and English versions are compact, front-load the core purpose, and each clause conveys a mode or a usage shortcut. There is no filler or repeated schema boilerplate.

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 small setter with no output schema and all-optional parameters, the description covers the mode vocabulary and key parameter relationship. It would be more complete if it explicitly listed required arguments per mode or stated the default when no args are provided, but those are inferable from the mode labels.

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 coverage is 100%, but the description adds value by mapping each mode to the relevant parameter concept and documenting the non-obvious shorthand that single may omit mode and pass frame directly. Conditional requirements per mode are not explicitly spelled out.

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 uses a specific verb ('set'), a precise resource ('frame range'), and enumerates the four modes. It clearly differentiates this configuration tool from siblings like render_frames by focusing on selecting frames rather than executing a render.

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 phrase 'set which frames to render' implies it is a configuration step, and the mode list gives selection guidance, but it does not explicitly direct the agent to sibling tools (e.g., render_frames/render_animation) for actually performing the render or state when not to use it.

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