set_frame

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

No annotations are supplied, so the description carries the full disclosure burden, yet it says nothing about whether the frame value is clamped to valid range, whether it triggers evaluation/cooking, or what happens with negative or out-of-range values. For a state-setting tool this is a meaningful gap.

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?

A single front-loaded sentence with no padding or redundancy. It is efficient, though its brevity comes at the cost of the missing details noted elsewhere rather than being a stylistic flaw.

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 tool is simple (one required numeric parameter, no output schema, no nesting), so an agent can plausibly invoke it. Still, with no annotations and no parameter documentation, the units and out-of-range behavior an agent would want before calling are absent.

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% for the single required 'frame' parameter, and the description adds only that it relates to the timeline. It does not specify units (frames vs seconds), accepted range, or whether fractional values are allowed, so the schema plus description still leave the parameter under-specified.

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 names a specific verb and resource: it sets the current frame of the timeline, which is unambiguous on its own. It does not, however, distinguish itself from near-neighbors like set_frame_range or set_playback_range, so the agent must infer the difference from names alone.

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?

There is no explicit guidance on when to use this instead of set_frame_range or set_playback_range, and no mention of prerequisites such as an open scene or timeline context. The only signal is the word 'current', which vaguely implies a single-frame scrub but leaves the alternatives unaddressed.

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