open_in_timeline

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

Annotations declare readOnlyHint=false, implying state change, but the description never says what that side effect is (does it create/modify a timeline tab or alter the project?). It also omits behavior when both clip and sequence are provided or when neither is, and says nothing about identifiers being resolved against an open project.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity comes at the cost of the missing information scored elsewhere.

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?

An output schema exists so return values needn't be explained, but for a 3-optional-parameter, non-read-only tool the description leaves critical gaps: which parameter selects the target, whether project is required for identifier resolution, and what the observable effect of opening is.

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 all three parameters are untyped-in-meaning optional strings with null defaults. The description mentions "sequence" and "clip" but adds no format details, no mutual-exclusivity rule, and never mentions the project parameter at all.

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+resource ("open ... in a timeline tab") that is distinguishable from most siblings, but it never contrasts with the closely related open_in_viewer tool, so the agent must infer the distinction between viewing and timeline editing.

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 guidance on when to use this versus open_in_viewer, no mention of prerequisites (must a project already be open?), and no note about whether clip or sequence should be supplied. Usage is left entirely to inference.

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