set_frame

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

The description implies a write operation by using 'set', which is appropriate. However, without annotations, it fails to disclose any side effects, such as whether setting the frame triggers renders or affects playback state, leaving the agent with basic but incomplete behavioral understanding.

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 unnecessary words. However, it could include a brief parameter hint without losing conciseness.

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 with no output schema, the description covers the basic purpose. However, it lacks parameter details and usage context, which are important given the large number of sibling tools.

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 single parameter 'frame' (integer) has no description in the schema (0% coverage) and the tool description adds no meaning—no range, unit, or constraints. This forces the agent to guess valid values.

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 'Set the current frame in the timeline' clearly states the verb ('set'), resource ('current frame'), and location ('timeline'), distinguishing it from siblings like 'anim_set_frame_range' and 'set_keyframe'.

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 is provided on when to use this tool versus alternatives such as 'anim_set_frame_range' or 'set_keyframe'. The description does not specify prerequisites (e.g., an existing timeline) or context.

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