export_to_davinci_resolve

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

With no annotations, the description must disclose behavior. It explains the tool creates an FCPXML file and describes the internal structure of each short. It does not mention overwrite behavior, error handling, or requirements beyond the integration. This is adequate but could be more comprehensive.

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 concise, using four sentences to cover purpose, output structure, compatibility, and requirements. Information is front-loaded and every sentence adds value without redundancy.

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?

Given the complexity (6 parameters, nested shorts array, no output schema), the description covers purpose, output structure, and a prerequisite. It lacks details on behavior of fps/width/height parameters and error conditions, but overall it provides a solid foundation for correct tool use.

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%, but the description adds value by explaining how parameters like captions_path (ProRes 4444 alpha overlay for V2) are used in the compound clip structure. This contextual information aids the agent in understanding the role of each parameter beyond the schema's property 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 clearly states the tool exports podcli shorts as a DaVinci Resolve FCPXML project, with specific output structure (compound clips with V1 and V2 overlays). It uniquely identifies this as an export action for DaVinci Resolve, distinguishing it from sibling tools like manage_integrations or create_clip.

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 explicitly requires the davinci_resolve integration to be enabled, providing a prerequisite. It also mentions compatibility with Resolve 20.x. However, it does not specify when not to use this tool or suggest alternatives, but given no other export tool, this is sufficient.

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