set_frame_range

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

IdempotentHint already signals repeat-safety, and the description adds partial-update behavior via 'start and/or end frame,' which is useful. It does not mention side effects or validation, but for a simple range setter this is a modest gap rather than a contradiction.

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?

One front-loaded sentence with no filler; the parenthetical adds the only necessary detail about the optional parameters.

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 two-parameter idempotent setter with an output schema, this description is nearly complete. The main missing context is an explicit relationship to sibling tools like set_playback_range, though the word 'scene' partially addresses that.

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%, and the description compensates by identifying start and end as frame bounds and signaling that either may be supplied. This is minimal but sufficient for two nullable integer parameters.

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?

Names the specific operation (set), resource (scene frame range), and supported fields (start/end). It is not a tautology and is unambiguous as a setter, but it does not explicitly distinguish itself from sibling set_playback_range.

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 'scene frame range' gives some context that this is scene-level rather than playback-level, but the description never states when to choose it over set_playback_range or set_frame, nor any exclusions. Usage is implied rather than explicit.

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