set_frame

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

The idempotentHint annotation already signals that repeated calls with the same frame are safe, and the description does not contradict this. The description adds no behavioral context beyond the annotation, such as whether the change affects rendering, viewport, or animation state, but the annotation covers the main safety concern.

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 short sentence with no wasted words, and the essential operation is front-loaded. It is appropriately concise, though it sacrifices semantic richness for brevity.

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 tool with one parameter, no output schema details, and no usage context, the description is incomplete. An agent cannot determine valid frame values, the relationship to set_frame_range, or what 'current frame' affects (viewport, render, animation). The idempotentHint helps but does not fill these gaps.

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 description coverage is 0%, so the description must compensate for the undocumented 'frame' parameter. The description only says 'Set the current frame' and does not explain what the integer represents (e.g., frame number, time in seconds, or index), nor its bounds or units. This is a significant gap for a tool with a single parameter.

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' states a clear verb and resource, and the single 'frame' parameter makes the operation unambiguous. However, it does not distinguish itself from the sibling 'set_frame_range' or 'playback_control', which are related frame/playback operations, so an agent must infer the difference from the parameter schema.

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 given on when to use this tool versus alternatives like set_frame_range or playback_control. The description does not mention context such as animation playback, scrubbing, or keyframe navigation, leaving the agent to guess the intended use case.

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