Final Cut Pro MCP Server

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

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the requirement for macOS speech recognition, which adds useful context about dependencies. However, it lacks details on permissions needed, whether it modifies existing clips, error handling, or output format. For a tool with zero annotation coverage, this is insufficient to fully inform an agent.

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 two sentences that are front-loaded and efficient. The first sentence states the core purpose, and the second adds a critical prerequisite. There is no wasted text, making it highly concise and well-structured.

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 tool has no parameters, no annotations, and no output schema, the description provides basic purpose and a prerequisite. However, for a tool that performs AI transcription, it lacks details on behavioral aspects like what 'selected clips' means, how captions are generated, or error conditions. This makes it minimally adequate but with clear gaps in completeness.

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, meaning no parameters need documentation. The description does not discuss parameters, which is appropriate. It earns a 4 because it focuses on the tool's purpose without redundant parameter info, aligning with the baseline for zero parameters.

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's purpose: 'Use AI to automatically transcribe audio in the selected clips to captions/subtitles.' It specifies the action (transcribe), target resource (audio in selected clips), and output format (captions/subtitles). However, it does not explicitly differentiate from sibling tools like 'import_captions' or 'export_captions', which is why it scores a 4 instead of a 5.

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 some usage context with 'Requires macOS speech recognition,' indicating a prerequisite. However, it does not specify when to use this tool versus alternatives like 'import_captions' or 'export_captions' from the sibling list, nor does it give explicit when-not-to-use guidance. This leaves usage somewhat implied rather than fully clear.

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