set_frame_range

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

No annotations are provided, so the description carries full burden. It fully discloses that this is a scene-write operation, is undoable, requires finite floats with start<=end, supports sub-frame end values, returns status=error on invalid inputs without writing, and persists on success via hou.playbar.setFrameRange. This is excellent transparency for a mutation tool.

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 highly concise, using two compact sentences. It front-loads the purpose, then packs validations and error behavior without fluff. Every sentence adds meaningful information.

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?

The description covers the core purpose, validations, error behavior, and persistence, but misses the meaning of ctx and the success return shape. Given no output schema, a brief note on success status would improve completeness. The tool is simple enough that this isn't critical, but the gap in ctx is noticeable.

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 must compensate. It explains constraints for start and end (finite floats, start<=end, sub-frame possible) but completely omits ctx. Without explanation, ctx remains ambiguous. This partially compensates for the schema gap but leaves a key parameter undocumented.

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 'Set global frame range' with a specific verb and resource. It mentions it's global and scene-writing, which distinguishes it from related tools like set_playback_range, though it doesn't explicitly name alternatives. Purpose is clear and specific.

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 explicit guidance on when to use this tool versus alternatives. The description notes it's global and writes to the scene, but there is no mention of preferred use cases or exclusions. Without context, the agent gets no direction on selecting this over similar tools.

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