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 full burden for behavioral disclosure. 'Zoom the timeline view' gives no information about what the tool actually does behaviorally—whether it's a read-only operation, if it modifies project state, what visual changes occur, or any side effects. It's completely inadequate for a tool with no annotation coverage.

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 extremely concise—a single three-word phrase. While this represents severe under-specification in terms of content, from a pure conciseness perspective it's maximally efficient with zero wasted words or redundant information.

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 with no annotations and no output schema, the description is completely inadequate. It provides minimal information about purpose, no behavioral context, and fails to explain what 'zooming' actually accomplishes in this video editing context. Given the complexity implied by the sibling tools and the lack of structured data, this description leaves the agent with insufficient guidance.

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 description coverage is 100%, with the single parameter 'action' fully documented in the schema with enum values and description. The tool description adds no additional parameter information beyond what the schema already provides, so it meets the baseline score of 3 for adequate coverage through structured data alone.

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 'Zoom the timeline view' is a tautology that essentially restates the tool name 'zoom_timeline' without adding meaningful specificity. It doesn't distinguish this tool from potential sibling tools that might also manipulate timeline views, nor does it specify what 'zoom' means in this context beyond the obvious.

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?

No guidance is provided about when to use this tool versus alternatives. The description doesn't mention any context, prerequisites, or exclusions, and with many sibling tools available (like 'navigate', 'go_to_timecode', or 'timeline_history'), there's no indication of when zooming is appropriate versus other timeline manipulation methods.

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