export_resolve_xml

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

No annotations provided; description only says 'simplified v1.9', hinting at limitations but not disclosing specifics. No mention of side effects, required permissions, or what happens to unsupported features.

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?

Single sentence efficiently conveys core purpose, but could benefit from adding a brief note on typical usage or output. Still, it is well front-loaded.

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?

Despite 3 parameters and no output schema, the description lacks details about the export process, error handling, overwrite behavior, or the actual return value. For a file-creation tool, this is insufficient.

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 covers all 3 parameters with descriptions. The tool description adds no additional parameter meaning beyond the schema, so baseline score of 3 is appropriate.

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?

Description clearly states verb 'Export', specific resource 'timeline', target format 'DaVinci Resolve compatible FCPXML (simplified v1.9)', which distinguishes it from sibling tools like export_csv, export_edl, and export_fcp7_xml.

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?

Usage is implied by the name and format, but there is no explicit guidance on when to prefer this over export_fcp7_xml or other export tools. No conditions or prerequisites are mentioned.

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