validate_current_timeline

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

With no annotations, the description carries full burden but only states the check action. It does not disclose what happens on failure (error vs. boolean), whether it is read-only, or any side effects. The existence of an output schema partially mitigates this, but the description adds no behavior details.

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 a single sentence, no wasted words, and starts with the verb 'Check' immediately stating the action. It is optimally concise.

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 validation tool with an output schema, the description is adequate but lacks context about dependencies (e.g., need a connection via validate_resolve_connection or a project via validate_current_project). This is a gap given sibling tools that imply a sequence.

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?

There are zero parameters (schema coverage 100%), so the description cannot add parameter-level meaning. It explains the tool's purpose, which is sufficient for an empty parameter list. Baseline 4 is appropriate.

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 checks availability of both a current timeline and playhead in Resolve, using a specific verb and resource. It distinguishes from sibling validation tools that check other aspects (e.g., project, clip, connection) and from retrieval tools like current_timeline.

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?

No guidance is provided on when to use this tool versus alternative validation tools (e.g., validate_current_project, run_full_validation). An agent would not know if this should be called before other operations or if it is a prerequisite for other tools.

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