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 the full burden of behavioral disclosure. It hints at 'advanced controls' and 'managing' but doesn't clarify if this is a destructive operation, requires specific permissions, has side effects, or details the response format. This is inadequate for a tool with potential audio modifications.

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 that front-loads the key information ('Advanced audio fade controls') without any wasted words. It's appropriately sized for the tool's complexity.

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 lacks behavioral details (e.g., mutability, side effects) and doesn't explain return values, which is insufficient for a tool that modifies audio fades in a professional editing 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%, so the schema fully documents the 'action' parameter with enum values and descriptions. The description adds no additional parameter semantics beyond implying general fade management, meeting the baseline for high schema coverage.

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 as 'Advanced audio fade controls for managing fade handles and crossfades,' specifying both the resource (audio fades) and actions (managing fade handles and crossfades). However, it doesn't explicitly differentiate from sibling tools like 'audio_operations' or 'adjust_volume,' which might also handle audio adjustments, keeping it from a perfect score.

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 mentions 'managing fade handles and crossfades' but doesn't specify contexts, prerequisites, or exclusions, leaving the agent to infer usage from the parameter enum alone.

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