Control Timeline Transport

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

Annotations already mark it as a mutation (readOnlyHint=false). The description adds valuable context: it returns the timeline state for verification, and it discloses the side effect of pausing freezing downstream chains. This exceeds what annotations alone convey.

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?

Three concise sentences: purpose, return value, and a side-effect warning. Every sentence earns its place and information is front-loaded.

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 tool with good annotations and 100% schema coverage, the description covers all essential aspects: actions, return behavior, and a notable side effect. No output schema exists, but the return value is described, so no critical gaps remain.

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 100%, so the baseline is 3. The description does not add parameter details beyond what the schema already provides; it only maps high-level actions to parameter names implicitly.

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 drives the TouchDesigner project timeline with specific verbs (play, pause, seek, jump, set rate), distinguishing it from sibling tools that manage cues or query info.

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?

Usage is implied through the enumerated actions, but the description does not explicitly state when to use this tool versus alternatives like manage_cue or execute_python_script, nor any exclusions.

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