render

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 states that a video file is produced and that 'mp4-project' preserves frame size, but it does not disclose whether output_path is overwritten, whether rendering is long-running, or what happens 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?

The description is two front-loaded sentences with no filler. The preset caveat is placed immediately after the purpose, making efficient use of the short space.

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 render tool with no annotations, no output schema, and 0% schema description coverage, the description is too sparse. An agent can infer the basic call, but lacks important context about return value, overwrite behavior, and render duration.

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%, so the description should compensate. It only explains the 'mp4-project' preset value; it does not clarify project_name or output_path semantics, such as whether the project must already exist or whether output_path is a file path with overwrite behavior.

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 states a specific verb and resource: 'Render a project to a video file with melt.' It clearly distinguishes the export/render operation from the project-editing siblings such as add_clip and trim_clip.

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 purpose implies it is the final export step, but there is no explicit guidance on when to use it versus alternatives or prerequisites such as requiring an existing project. Usage is implied rather than documented.

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