export_sequence

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool performs a render and export operation, implying it is a write/mutation tool that creates files, but does not disclose critical behaviors such as processing time, file overwriting risks, required permissions, or system resource usage. The description is minimal and lacks operational context.

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 concise with two sentences that directly state the tool's function and purpose. It is front-loaded with the core action ('Renders and exports a sequence to a video file') and avoids unnecessary details. However, the second sentence ('This is for creating the final video.') is somewhat redundant and could be integrated more efficiently.

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?

Given the complexity of a video export tool with 6 parameters, no annotations, and no output schema, the description is incomplete. It lacks information on behavioral traits (e.g., processing behavior, error conditions), output details (e.g., file format specifics, success indicators), and usage context. The description does not compensate for the absence of structured metadata.

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 schema fully documents all parameters. The description adds no parameter-specific semantics beyond what the schema provides (e.g., it does not explain relationships between parameters like 'presetPath' overriding 'format' or 'quality'). Baseline score of 3 is appropriate as the schema handles parameter documentation adequately.

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's purpose: 'Renders and exports a sequence to a video file' with the goal of 'creating the final video.' It specifies the verb ('renders and exports'), resource ('sequence'), and output ('video file'), but does not explicitly differentiate from sibling tools like 'export_frame' (which exports a single frame rather than a full sequence).

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?

The description provides no guidance on when to use this tool versus alternatives. It mentions 'This is for creating the final video,' but does not specify prerequisites (e.g., whether the sequence must be edited first), exclusions, or comparisons to sibling tools like 'export_frame' or 'save_project_as' for other output types.

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