export_xml

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the key default behavior (None means no file write and XML is returned in data.xml) and that a path causes a write, but it does not mention overwrite behavior, permissions, or whether XML is also returned when output_path is provided.

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 compact and front-loaded with the tool's purpose before covering the argument. Every sentence adds information, with no filler or restatement of the tool name.

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 tool with one optional parameter and an output schema, the description covers the main calling concern and the None behavior. It could more explicitly state what happens in the non-None branch, but the overall guidance is sufficient for an agent to call it correctly.

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?

Although schema description coverage is 0%, the description fully compensates by explaining the single parameter's type, giving a concrete file-path example, and specifying the exact behavior when output_path is None. This is materially more useful than the schema's bare title and default.

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, resource, and output format: 'Generate Kdenlive/MLT XML for the current project.' This clearly differentiates it from siblings like export_render and export_list_presets by output type, though it does not explicitly name the alternative tool to use for other export kinds.

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?

Provides clear context by explaining the single optional argument and what happens when it is omitted (no file written; XML returned in data.xml). It does not explicitly state when to prefer export_xml over export_render, so no exclusion guidance is given, but the intended usage is easy to infer.

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