timeline_set

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

With no annotations provided, the description carries the behavioral disclosure burden. It does describe the immediate effects: changing cook rate, toggling real-time playback, and jumping to a frame. However, it does not mention return values, whether changes are persistent, or any side effects beyond the direct settings.

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 compact and front-loaded with the core purpose, followed by a clean parameter reference. Every sentence adds useful information and there is no redundant or promotional text.

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 setter with three optional parameters and no output schema, the description covers the key facts an agent needs: what each parameter does and how they combine. It could mention return behavior or the no-op case when all parameters are null, but these are minor 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?

The schema provides only types and defaults, while the description adds meaningful semantics for all three parameters: 'Desired cook rate (fps)', 'Enable/disable real-time playback', and 'Jump to this absolute frame'. This fully compensates for the 0% schema description coverage.

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 opens with a specific verb and resource: 'Set cookRate, realTime and/or jump to a frame.' It clearly states what the tool does and enumerates the exact targets, making it easy to distinguish from siblings like timeline_get, timeline_play, and timeline_pause.

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?

The description does not explicitly say when to use this tool versus alternatives, nor does it provide any exclusions or prerequisites. It implies usage through the action verb 'Set' but gives no guidance about choosing timeline_set over timeline_play, timeline_pause, or timeline_get.

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