set_frame

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

The idempotentHint annotation already indicates repeated calls are safe, and the description adds no additional behavioral context such as side effects on viewport or timeline. It doesn't contradict annotations, but it provides no extra value beyond the annotation.

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 concise at one sentence, but it's under-specified. While it has no fluff, it lacks important details that could be included without bloating.

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?

Despite the tool being simple, the description fails to explain the semantics of the frame parameter or the effect of setting it. The output schema exists, so return values are covered, but the missing parameter details make it incomplete.

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 only specifies 'frame' as an integer with no description, and the description does not explain what frame means (e.g., 0-indexed vs 1-indexed, whether it's frame number or time). With 0% schema description coverage, more compensation was needed.

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 tool sets the current frame with a verb+resource structure. However, it doesn't differentiate from sibling tools like set_frame_range, and 'frame' could be interpreted as frame number or object 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?

No usage guidance is provided. The description does not indicate when to use set_frame versus set_frame_range, playback_control, or frame_selected, nor any prerequisites.

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