anim-set_frame

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

With no annotations, the description carries the behavioral burden. It states the direct effect (sets the current scene frame), which is appropriate for a simple setter. However, it does not disclose potential clamping behavior, range constraints, or whether playback state is affected.

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 concise sentence that conveys the core action with no filler. It is appropriately front-loaded and effectively scannable.

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-param action, the description is minimally adequate. It could still be more complete by mentioning usage context, likely range rules, or clarifying that it does not insert/remove keyframes. Nonetheless, the operation is trivial enough that the description is not severely lacking.

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 needs to compensate for parameter meaning. It does not explain the 'frame' parameter beyond the schema's own property title. The description adds no additional detail about frame values, intervals, or special cases.

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 uses a specific verb ('Set') and clearly identifies the resource ('current scene frame/playhead'). It is distinct from siblings like anim-set_timeline and anim-insert_keyframe, though it does not explicitly mention those distinctions.

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?

There is no guidance on when to use this tool versus alternative animation tools, no context about prerequisites, and no exclusion statements. The sibling tools include similarly named setters, so this gap matters.

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