project.create_kdenlive

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'create', but does not mention overwrite behavior, output path handling, side effects on input files, or permission requirements. Key parameters like overwrite and output_path are left unexplained.

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 a single, front-loaded sentence with no wasted words. It immediately states the action and the required inputs, earning a perfect score for conciseness and structure.

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?

While an output schema exists, the description gives no workflow context, prerequisites, or behavior around the optional parameters. For a tool with five parameters and no annotations, this minimal description is insufficient for an agent to invoke it correctly, especially without understanding overwrite and output_path semantics.

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%, and the description names none of the five parameters. Even though parameter names like input_path and subtitles_path are somewhat self-explanatory, the description adds no semantic detail about how these parameters interact or what values are expected, failing to compensate for the schema's lack of descriptions.

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 uses a specific verb ('Create') and resource ('editable Kdenlive project') with clear input sources ('video and SRT file'), which makes the tool's purpose unmistakable. It also distinguishes from sibling tools like video.transcribe or video.caption, which perform different operations.

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 description implies the tool is for creating an editable project from an existing video and SRT, but it does not explicitly state when to use this tool versus alternatives. No exclusions or alternative tool references are provided, making it minimally adequate.

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