anim_goto_frame

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

Annotations already indicate this is not read-only and has a destructive hint. The description adds meaningful detail beyond that: it sets the current time slider position and does not trigger playback. This clarifies the practical effect of the mutation, though 'locates only' could downplay the destructive hint.

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 extremely compact, with the core action and the key behavioral caveat ('does not play') front-loaded. Both English and Chinese versions serve the same clear purpose without unnecessary elaboration.

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?

This is a simple single-parameter tool with a clear action, and the description covers the essential behavior. There is no output schema, but none is needed for a navigation/setting operation; minor details like frame range clamping or return value are not critical here.

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 coverage is 100% and the parameter description ('Target frame') already explains frame. The tool description reinforces the meaning by linking the frame to the time slider but adds no significant semantic information beyond the schema.

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/set), a clear resource (current time slider/frame), and an explicit boundary: 'does not play.' This distinguishes it from playback and frame-reading siblings like anim_play and anim_get_frame without needing to inspect schemas.

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 phrase 'Locates only, does not play' gives a clear usage context: use it to position the time slider without starting playback. It provides a relevant exclusion, though it does not name alternative tools such as anim_play or anim_get_frame explicitly.

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