Final Cut Pro MCP Server

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

With no annotations, the description carries full burden but only states the action generically. It doesn't disclose behavioral traits such as whether navigation affects playback, requires a timeline selection, has side effects (e.g., moving playhead), or any constraints (e.g., availability based on timeline state), missing key operational context.

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 with no wasted words, making it front-loaded and easy to parse. However, it's overly terse, lacking necessary detail for a tool with no annotations, which slightly reduces its effectiveness.

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 no annotations and no output schema, the description is incomplete. It doesn't explain what 'navigate' means in practice, expected outcomes (e.g., cursor movement), or how it interacts with the timeline, leaving significant gaps for a tool with one parameter but critical behavioral context.

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 action parameter fully documented via enum values. The description adds no meaning beyond the schema, as it doesn't explain parameter implications (e.g., what 'jump_to_start' does). Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Navigate through the timeline' states a general purpose but is vague about what 'navigate' entails. It doesn't specify the exact resource (e.g., timeline cursor/playhead) or differentiate from sibling timeline tools like 'go_to_timecode' or 'timeline_history', though it implies movement within a timeline context.

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 on when to use this tool versus alternatives. It doesn't mention prerequisites, context (e.g., timeline must be open), or compare to siblings like 'go_to_timecode' for specific timecode jumps, leaving the agent to infer usage from the action parameter alone.

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