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 carries the full burden of behavioral disclosure. 'Render the timeline' vaguely implies a processing or output operation but fails to specify critical traits such as whether it's destructive, requires specific permissions, has rate limits, or what the output entails (e.g., file generation, preview). This leaves the agent guessing about the tool's behavior and impact.

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?

While concise with a single sentence, the description is under-specified rather than efficiently informative. It lacks front-loaded critical details (e.g., what rendering produces), making it ineffective despite its brevity. Conciseness should not come at the cost of clarity.

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 implied by sibling tools in a video editing context (e.g., 'export_xml', 'transcode_media'), the description is severely incomplete. With no annotations, no output schema, and a vague purpose, it fails to provide enough context for an agent to understand the tool's role, behavior, or output, making it inadequate for safe and effective 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?

The input schema has 100% description coverage, with a clear enum parameter 'scope' documented as 'Render all or just the selection'. The description adds no additional parameter semantics beyond this, but since the schema is comprehensive, the baseline score of 3 is appropriate as it doesn't need to compensate for gaps.

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 'Render the timeline' is a tautology that essentially restates the tool name 'render' with minimal added context. While it specifies the resource ('timeline'), it lacks specificity about what rendering entails (e.g., generating a video file, preview, or export) and doesn't distinguish it from sibling tools like 'export_xml' or 'transcode_media', which might involve similar output 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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a timeline ready), exclusions, or comparisons to sibling tools like 'export_xml' or 'transcode_media', leaving the agent with no context for appropriate selection.

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