Timeline playback

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

With no annotations, the description carries the full behavioral burden and falls short: it never says whether playback is blocking or asynchronous, whether it mutates project state permanently, which parameter is required for which action, or what happens on error. The 'action' string has no enum, so valid values (only 'set_time' is visible via the schema default) are left to guesswork.

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 tight sentence with the resource and operations front-loaded and no filler. It is efficient, though its brevity contributes to the specification gaps elsewhere rather than being purely a virtue.

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?

No annotations, no output schema, and 0% schema coverage leave the agent without the essentials for a state-mutating timeline tool: valid action values, which params each action needs, default vs explicit animation targeting, and return/async behavior are all absent.

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% and the description only loosely maps to the params: 'set the time' hints at 'time', and the verbs hint at 'action' values. The 'animation' parameter is entirely unexplained — no indication whether it is a name, ID, or defaults to the active animation.

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 gives a specific verb ('control') and resource ('the animation timeline') plus the concrete operations (set time, play, pause, stop). It is clearly distinct from create/set/delete_animation siblings, though it never explicitly contrasts itself with the adjacent bb_step or bb_list_animations tools.

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?

It enumerates the operations but gives no when-to-use context, no prerequisites, and no routing away from alternatives like bb_step or bb_add_keyframe. The agent must infer from the tool name when this is the right call versus manipulating the animation state directly.

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