revideo_render_job

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

No annotations exist, so the description carries the full behavioral burden. It names the four stages, which is useful, but says nothing about side effects: whether output_path is overwritten, whether install requires network access, what happens on timeout, or whether the operation is idempotent. For a heavy multi-stage job runner this is a significant gap.

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?

A single front-loaded sentence with the verb chain first and the scope qualifier last. Zero waste, though it is arguably under-specified rather than concise for a pipeline of this complexity.

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 need not be explained, but this is a complex nested-parameter, six-argument, multi-stage tool with no annotations and no documented parameters. The description lists the stages but leaves prerequisites, failure behavior, and argument meaning entirely unaddressed.

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% across six parameters, so the description must compensate and does not. It adds no meaning to job, work_dir, output_path, scene_source, render_timeout, or install_timeout beyond repeating the word 'job' and the scope adjective 'local'.

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 compound verb chain (materialize, install, render, verify) against a specific resource (one local Revideo job). This implicitly distinguishes it from the single-stage siblings revideo_materialize, revideo_install, and revideo_render, though it never explicitly says it is the end-to-end orchestrator of those three.

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 when-to-use or when-not-to-use guidance is given. The presence of near-identical siblings (revideo_materialize, revideo_install, revideo_render) makes the choice genuinely ambiguous, and the description offers no rule for selecting this pipeline over the individual steps.

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