reformat_timeline

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

The description indicates the tool creates a new file (non-destructive), but with no annotations provided, it does not disclose potential side effects like cropping or letterboxing that may occur with aspect ratio changes. The behavioral context is adequate but minimal.

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, clear sentence with no extraneous words. Every word contributes to purpose, making it highly concise.

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 minimal. It fails to mention that output_path is optional and defaults to a suffix, nor does it describe the return type. For a simple tool, the description is adequate but not complete.

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 100%, so the baseline is 3. The description adds little beyond the schema: it lists example formats but does not explain the 'custom' option or how width/height interact. It provides no additional semantic value.

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 creates a new FCPXML with a different resolution or aspect ratio, and gives examples like 9:16 for TikTok. However, it does not explicitly distinguish this tool from siblings that also produce output files, such as export_csv.

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 implies usage for reformatting timelines to specific aspect ratios, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., when to choose 16:9 vs custom), nor does it mention prerequisites or limitations.

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