set_frame

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

With no annotations provided, the description must fully disclose behavior. It only states the action and return type, but omits side effects, prerequisites (e.g., valid timeline), or constraints (e.g., frame range limits).

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 very concise, using two sentences plus an Args/Returns list. It is front-loaded with the action and minimally structured.

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 1-parameter tool, the description is adequate but incomplete. It lacks details on valid frame range, whether the operation is undoable, and what happens if the frame is out of bounds. Given no annotations or output schema, more context is needed.

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 schema has 0% description coverage. The description merely repeats 'Frame number' from the parameter name without adding meaning (e.g., valid range, type constraints beyond integer). It does not compensate for the schema's lack of description.

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 states the action ('set the current frame') and the resource ('timeline'). It distinguishes well from sibling tools like set_frame_range or insert_keyframe by specifying it sets a single frame.

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 implies usage (to change the current frame) but does not provide explicit guidance on when to use this tool versus alternatives such as set_frame_range or insert_keyframe. No exclusions or prerequisites are mentioned.

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