set_frame

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

No annotations are provided, so the description carries the full burden. It confirms a state mutation ('Set the current frame') but says nothing about side effects such as triggering re-evaluation/cook, valid frame bounds, or return behavior. For a mutation tool with zero annotation coverage, this is a notable 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?

The one-line purpose is front-loaded and tight, but the 'Args:' block duplicates the schema's parameter definition without adding information, slightly wasteful though not egregious.

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 simple one-parameter setter, the absence of annotations and output schema means the description should cover evaluation side effects, valid ranges, and relationship to sibling range-setting tools. None of that is present, leaving the definition under-complete.

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, but its 'frame: Frame number.' merely restates the parameter name and title. It does not clarify whether the value is integer-only (the schema types it as 'number', allowing fractions), the acceptable range, or how it relates to the global timeline.

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 clear verb+resource ('Set the current frame in the timeline') that an agent can immediately understand. However, it offers no differentiation from close siblings like set_frame_range, set_playback_range, or get_frame, so scope against alternatives must be inferred.

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 guidance on when to use this versus set_frame_range, set_playback_range, or related timeline tools. It never states prerequisites (e.g., a scene must be loaded) or context of use; usage is entirely implied.

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