start_change_format

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

No annotations provided. Description mentions non-re-encoding, caching behavior via force_run, and immediate return of job_id+status. However, it doesn't disclose potential side effects (e.g., overwriting files) or permissions.

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?

Description is concise: three sentences plus parameter explanations, front-loaded with core action. No redundant information.

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?

Covers core functionality and parameters. Mentions async nature via 'Returns immediately with job_id + status'. Output schema exists, so return values not needed. Lacks details on output file location or persistence.

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 fully defines each parameter: input_file must exist, output_format with examples and optional dot, and force_run behavior. This adds essential meaning beyond the schema 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 tool converts video to another container format without re-encoding, using specific verbs 'Enqueue' and 'Converts'. It distinguishes from siblings like start_change_resolution by focusing on container format change.

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 like start_change_resolution or start_audio_extraction. Does not specify prerequisites or context.

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