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

No annotations are provided, so the description carries the full behavioral burden. It never states that this is a mutation that kicks off a potentially long-running/expensive render, whether execution is synchronous or async, what auth or permission model applies, or what happens to the workspace on failure.

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?

Two tight sentences with the core action front-loaded and no filler. Slightly under-specified rather than over-long, but structurally clean.

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 workflow-invocation tool with no annotations, no output schema, and a free-form nested inputs object, the description omits what the call returns (job ID, outputs, artifacts), async/latency behavior, and the relationship to the sibling execute_workflow. This is a material gap for an agent needing to call it correctly.

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 adds a little context about inputs containing URLs and arbitrary scalar fields, but this is largely redundant with the schema's "keyed by input label and/or node ID" note.

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?

States a clear verb ("Run") and a specific resource (a Sequencer workflow API endpoint) and scopes it to the video editor context. However, it does not distinguish itself from the very similar sibling execute_workflow, leaving the agent to guess which execution tool applies.

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 on when to use this versus execute_workflow, run_production_template, or other run/execute siblings. There are no prerequisites, no exclusions, and no indication of the required API-access workflow precondition beyond the schema field description.

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