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 full burden for behavioral disclosure. It states the tool's function but reveals nothing about permissions needed, whether it modifies clips destructively, how it handles errors, or what visual feedback to expect. For a tool that likely alters media, this lack of transparency is inadequate.

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, well-structured sentence that efficiently communicates the core function and purpose. Every word earns its place with no fluff or repetition, making it easy to parse quickly.

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 that performs color matching (likely a media-altering operation), the description is insufficient given no annotations and no output schema. It lacks critical context about side effects, success indicators, or error conditions that an agent would need to use this tool responsibly in a video editing workflow.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description appropriately focuses on the tool's purpose without redundant parameter explanations, meeting the baseline for zero-parameter tools.

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 specific action ('match the color') and target resources ('selected clip' and 'reference clip'), with a clear purpose ('for consistent color grading across scenes'). It distinguishes itself from siblings like 'color_board' or 'color_correction_nav' by focusing on matching rather than general color 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 implies usage when color consistency is needed across scenes, but provides no explicit guidance on when to use this tool versus alternatives like 'add_color_correction' or 'color_board'. No prerequisites, exclusions, or comparisons to sibling tools are mentioned.

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