fcp_navigate

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

Description mentions 'Opens timecode entry if provided' but fails to disclose side effects or prerequisites. Without annotations, the description should cover behavioral traits like whether it moves the playhead or requires an open project.

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?

Two sentences with an args list, front-loaded with purpose. Every sentence is meaningful and there is no wasted text.

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 simple navigation command, the description is mostly complete. It could mention that FCP must be running or that it acts on the current timeline, but the presence of an output schema reduces the need for return value details.

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 coverage is 0%, but the description adds value by providing an example format ('00:01:30:00') and explaining the parameter purpose beyond the schema's type string.

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 verb 'Navigate' and the specific resource 'timecode in FCP', distinguishing it from sibling tools that perform different actions like exporting, playback, or applying effects.

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 a timecode format example, implying when to use, but does not explicitly state when not to use or suggest alternatives. No comparison to other navigation methods.

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