fcpxml_change_speed

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

No annotations provided, so description must bear the burden. It says 'Change' implying mutation, but does not disclose if it modifies in-place or creates new file, nor any side effects or permissions. The output_path parameter hints at writing to new file but is not explicitly stated.

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 short and front-loaded with the action. The argument list is clear and uses a consistent format. However, the action sentence could be more descriptive (e.g., 'Modifies the playback speed of a clip in a Final Cut Pro XML file').

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?

The tool is simple and the description covers the basic inputs. However, it lacks explanation of output behavior (even though output schema exists), and doesn't specify that the tool creates a new file (inferred from output_path). For a mutation tool with no annotations, more context is needed.

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?

With 0% schema description coverage, the description adds meaningful explanations for all 4 parameters, especially speed_factor with examples (2.0 = 2x fast). This significantly aids understanding beyond the schema's titles.

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 action 'Change clip playback speed' with a specific verb and resource. It distinguishes itself from sibling fcpxml_* tools like trim or split by focusing on speed.

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 on when to use this tool vs alternatives (e.g., when to use fcpxml_change_speed vs other fcpxml manipulation tools). No context on prerequisites or exclusions.

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