set_current_frame

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

With no annotations and a minimal description, the tool does not disclose any side effects, such as whether it changes the active time or triggers updates. The description '跳到某帧' simply states the action without elaborating on state changes, dependencies, or potential consequences. This leaves the agent unaware of what happens beyond the immediate call.

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, clear sentence with no extraneous words. It efficiently conveys the core action. The structure is highly concise and avoids unnecessary detail, which is appropriate for such a simple operation.

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 is too sparse to be complete. It lacks context about what 'frame' means, whether the frame index is 0-based or 1-based, what happens if the frame is out of the current range, and whether it affects any subsequent operations. Given the minimal schema and no annotations, the tool description leaves critical ambiguities unresolved.

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 parameter 'frame' has type integer but no description in the schema. The tool description does not clarify whether it is a zero-indexed frame number, a time-based value, or what valid range applies. Since schema coverage is 0% and the description adds no meaning, the agent has insufficient information to provide a correct value confidently.

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 indicates setting the current frame position. It uses the verb 'jump' and specifies the resource 'frame', which distinguishes it from siblings like 'set_frame_range' that operate on ranges. However, it is slightly ambiguous because it does not explicitly mention the timeline or animation context, though this is inferable from sibling tools.

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 guidance on when to use this tool versus alternatives. It does not mention that it is the appropriate choice for moving the playhead or setting the current frame index, nor does it contrast with related tools such as 'set_frame_range' or 'insert_keyframe'. The description provides no situational context.

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