Render project

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

Goes well beyond the annotations: it discloses blocking behavior, the timeout escape hatch, ffprobe validation of the output, refusal conditions (existing output, unknown presets, missing media), and the important safety detail that the old file is replaced only after a successful validated render. This explains why destructiveHint=true despite 'Never modifies the project or its media' — the destruction is limited to the output path.

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?

Front-loaded with the core action and mechanism, then proceeds to guarantees and refusal conditions in a logical order. Four dense sentences with little waste, though the refusal enumeration is slightly packed and could be split for faster scanning.

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 long-running, potentially destructive render tool, the description covers blocking semantics, timeout, validation, refusal/overwrite safety, and the unsaved-changes caveat. With an output schema present, no return-value explanation is needed, so nothing an agent needs to invoke this correctly is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds real semantics: timeout_seconds truncates the blocking render, overwrite=true is required for an existing output and replacement is deferred until validation succeeds, and unknown presets are refused. These constraints are not inferable from the schema alone.

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 specific verb and resource ('Render a Kdenlive project to a new local file') plus the mechanism (kdenlive --render) and post-step (ffprobe validation). An agent can distinguish it from siblings like inspect_project, list_render_presets or probe_media without opening any schema.

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?

Gives clear usage context: it blocks until completion or timeout, and it explicitly covers the edge case that it renders the on-disk file rather than unsaved changes in a running Kdenlive. It does not explicitly name an alternative sibling to call first (e.g., list_render_presets for preset discovery, which only appears in the schema), so the when-to-use-vs-alternative guidance is clear but not fully explicit.

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