Final Cut Pro MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it indicates this opens a dialog (suggesting user interaction rather than automated processing), it doesn't disclose whether this requires specific permissions, whether it's destructive to media files, what happens if no clips are selected, or what the expected user flow is after the dialog opens.

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, efficient sentence that communicates the core purpose without any wasted words. It's appropriately sized for a simple tool that opens a dialog, and the information is front-loaded with the essential action.

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 zero-parameter tool with no output schema, the description adequately explains what the tool does at a basic level. However, given the lack of annotations and the fact this appears to be a UI interaction tool (opening a dialog), more context about the expected user workflow and what happens after the dialog opens would be helpful for an AI agent.

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 tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the parameter situation. The description appropriately doesn't waste space discussing parameters that don't exist, earning a baseline score of 4 for this zero-parameter tool.

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 action ('Open the transcode media dialog') and the target ('for the selected clips'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from sibling tools like 'render' or 'consolidate_files' which might also involve media processing 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 provides minimal guidance - it indicates this tool should be used when you want to open a transcode dialog for selected clips. However, it offers no guidance on when to use this versus alternatives like 'render' or 'consolidate_files', nor does it mention any prerequisites (like needing clips to be selected first).

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