export_to_davinci_resolve

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the output structure (compound clips with V1 and V2 tracks), compatibility (Resolve 20.x), and the integration requirement, which is substantial. However, it does not mention potential side effects like overwriting existing files at the output path, which is a minor gap.

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 three sentences with no filler, front-loading the core purpose and then providing structural and prerequisite details. Every sentence contributes actionable information, making it highly efficient.

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?

The description covers the essential aspects: purpose, output structure, compatibility, and integration requirement. It doesn't mention the logo_path parameter's role in the output (schema does), nor does it discuss error handling or file overwrite behavior. Given the complexity of the nested shorts array, the description is reasonably complete but could include a note on the resulting file behavior.

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?

The input schema already has 100% coverage, so the baseline is 3. The description adds value by mapping shorts fields to video tracks (V1 source, V2 captions) and explaining the compound clip concept, which goes beyond the schema's individual field 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 states a specific verb (export) and resource (podcli shorts to DaVinci Resolve FCPXML project), distinguishing it from any sibling tool. It clearly communicates the output format and target application, leaving no ambiguity about what the tool accomplishes.

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 provides a clear prerequisite (integration must be enabled) and how to enable it, which is essential context for using the tool. While it doesn't explicitly name alternatives or exclusion conditions, no sibling tool performs a similar export, so the guidance is adequate for the context.

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