revideo_materialize

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

No annotations are provided, so the description carries the full disclosure burden. It hints at one precondition ('validated job') but says nothing about whether materialization is idempotent, whether it overwrites existing files at 'dest', what permissions or pinned state are required, or what side effects occur on disk. For a mutation-style tool 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 no filler or repetition. It is efficiently written; the shortfall is under-specification rather than verbosity, so it scores well on structure without reaching the top of the scale.

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?

With an output schema present, return values need not be described, but the input side is badly under-covered: a nested object parameter, a required destination string, and an optional scene source are all undocumented while annotations are absent. The description does not supply enough for an agent to call this correctly on the first attempt.

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 three parameters, so the schema contributes nothing. The description only gestures at 'job' (the validated job) and possibly 'scene_source' ('pinned Revideo project'); the required 'dest' parameter is never explained, and 'job' is a free-form nested object with additionalProperties allowed and no documented shape.

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 names a verb ('Materialize') and a resource ('Kinocut's pinned Revideo project'), which is more than a tautology, but 'materialize' is unexplained domain jargon — the agent cannot tell whether it scaffolds files, copies assets, or hydrates a project. It also gives no basis for choosing it over siblings revideo_render, revideo_render_job, or revideo_install, all of which sit in the same namespace.

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 phrase 'for a validated job' implies a prerequisite state, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent has no way to know whether this precedes or replaces revideo_render_job. No exclusions or sequencing guidance is offered.

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