blender_timeline

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

With no annotations, the description carries the full behavioral burden. It does disclose one genuinely useful trait — that jumping to a frame evaluates existing keyframes — but omits that this is a state mutation (it changes the scene's current frame), whether partial input is allowed, and what happens to keyframes when fps changes.

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?

A single front-loaded sentence with no filler. It is slightly dense with slashes and "and/or", but every clause carries information.

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 four-parameter, no-annotation, no-output-schema tool, the description is minimal but not empty. It leaves out whether the tool requires an active Blender session, whether changes are persistent/saved, and how partial parameter combinations are handled.

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 coverage is 0%, so the description must compensate for four undocumented parameters. It does map loosely onto them (frame range = start/end, fps = fps, frame = frame), but never explains the null defaults, valid ranges, or how start/end interact when only one is supplied.

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 names a specific verb set ("Set", "jump to") and resources ("frame range", "fps", "frame"), so the agent knows this controls timeline state. It is distinguishable from sibling tools like blender_render or blender_key_pose, though it bundles three distinct operations into one sentence without separating them.

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 statement of when to use this tool versus alternatives, nor any precondition (e.g., Blender must be running, a scene must be loaded). The parenthetical "which evaluates existing keyframes" hints at a side effect but gives no guidance on when that matters.

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