blender_animation_goto_frame

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Jump to a specific frame in the timeline' clearly conveys that this is a non-destructive navigation action affecting the current frame. It does not mention whether playback is stopped or whether the change can be undone, but for such a simple operation the core behavior is transparent enough.

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 a single, efficient sentence with no filler. The core action is front-loaded and every word contributes to meaning, making it easy for an agent to parse quickly.

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 one-parameter seek operation with no output schema, the description plus schema fully cover what an agent needs to invoke the tool correctly. Nothing operationally important is missing, and the sibling ambiguity is minimal given the clear 'jump to frame' semantics.

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?

The input schema fully describes the only parameter ('Frame number to jump to') with 100% coverage. The description adds no extra semantic nuance beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb ('Jump') and a specific resource ('a specific frame in the timeline'). It also implicitly distinguishes itself from sibling tools like blender_animation_play and blender_scene_set_frame_range, making the tool's purpose unambiguous.

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 description gives no guidance about when to use this tool versus alternatives such as setting the frame range or playing the animation. There is no mention of context, prerequisites, or exclusions, so the agent must infer usage from the name alone.

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