Queue and trigger a 1080x1920 MP4 render at 15,000 Kbps to your chosen output directory and filename.
Queues and triggers 1080x1920 MP4 render (15,000 Kbps).
| Name | Required | Description | Default |
|---|---|---|---|
| filename | Yes | ||
| output_dir | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description only says 'queues and triggers' and omits whether the call blocks, how long it may run, whether existing files are overwritten, or failure behavior.
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?
Single concise sentence that immediately conveys the tool's core action and output format/resolution.
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?
Adequate for basic selection but lacks operational context such as output behavior, preconditions, and relation to render status/transport workflow.
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 provides no parameter descriptions and the description does not explain output_dir or filename beyond their names, missing details like required extension or path expectations.
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?
Clearly states the tool queues and triggers a specific render job with resolution and codec details, differentiating it from sibling tools like status or transport.
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 render command relative to siblings or what preconditions (e.g., timeline ready, project loaded) should exist before invoking.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.