clip_format_convert

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

With no annotations, the description must carry behavioral disclosure, but it only states the surface conversion and an 'optional scale and pad' that is not represented in the schema. It omits whether the input is modified, where the output goes, or how padding behaves, making the behavior under-specified and partly misleading.

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 front-loaded sentence with no filler, and the supported formats are listed compactly. It loses a point because 'pad' is a behavioral claim that is not backed by the schema.

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 4-parameter processing tool with no annotations and no output schema, this description is not complete enough. It lacks usage context, parameter details, output location, and behavior on the input file, so an agent would still need to guess key calling conventions.

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 0%, so the description must compensate, but it only hints at format and scaling without naming the required 'input' or explaining width/height semantics. 'Pad' does not map to any parameter, leaving the parameter model ambiguous.

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 identifies a conversion action with specific target formats (MP4, MOV, MKV, WebM) and optional resizing, which distinguishes it from the clip_* manipulation siblings. It does not explicitly name an alternative tool, but the verb+resource combination is unambiguous.

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?

There is no indication of when to use this tool instead of clips like clip_crop, clip_speed, or media_import, nor any prerequisites or output expectations. Context must be inferred entirely from the tool name.

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