add_timeline_node

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

With no annotations, the description carries the full behavioral burden. It clearly discloses that the tool mutates a blueprint by adding a node, and it describes the return value (node_id and pins). However, it does not mention side effects such as duplicate timeline names, whether the blueprint must be saved/compiled, or other mutation consequences.

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 well-structured with a short summary, Args section, Returns section, KB reference, and example. Some argument lines ('Blueprint name', 'Name for the timeline') are somewhat tautological, but overall the format is efficient and front-loaded with the most important context.

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?

The description covers purpose, arguments, return contract, a knowledge-base pointer, and a usage example, which is quite complete for a 5-parameter tool. It could be improved by detailing valid track types beyond the example, the exact format of node_position, and behavior for name collisions, but nothing essential is missing for basic correct invocation.

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 descriptions are completely absent (0% coverage), so the description is the only source of parameter meaning. It explains every parameter: blueprint_name, timeline_name, tracks with a concrete example dict, length with units (seconds), and node_position as optional. This fully compensates for the empty schema descriptions.

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 states a specific action and resource: 'Add a Timeline node for smooth interpolation animations.' It also explains what Timeline nodes do (play float/vector curves over time), which distinguishes this from other blueprint-node tools that add different node types.

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?

Provides clear use context with practical examples ('great for doors opening, lights fading') and clarifies that timelines animate curves over time. It does not explicitly mention alternatives or when not to use it, but the context is strong enough for an agent to select it appropriately among the many add_* sibling tools.

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