ffkit_transcode

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

With no annotations provided (no readOnlyHint, destructiveHint, etc.), the description carries the full burden of behavioral disclosure. It mentions that 'the output container is inferred from the file extension,' which is a useful behavioral trait. However, it does not disclose whether the operation is destructive (e.g., overwrites output), whether it requires disk space for the output, or details about error handling (e.g., what happens with invalid codecs).

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 sentence followed by a brief note about container inference. It is concise and front-loaded with the main purpose. One could argue it could be slightly longer to add usage guidelines or behavioral notes, but it is not overly verbose.

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 the tool's complexity (9 parameters, 2 required) and lack of output schema or annotations, the description is adequate but not complete. It explains the core function and one important inference, but it lacks guidance on parameter relationships (e.g., interaction between bitrate and CRF) and error behavior. A more complete description would also mention typical usage patterns.

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 100%, meaning all 9 parameters have descriptions in the input schema. The description adds minimal semantics beyond the schema: it mentions that the output container is inferred from the extension, which relates to the output_path parameter. For the most part, the description does not add substantial meaning over what the schema already provides.

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's purpose: 'Transcode a media file to a different format, codec, or resolution.' It specifies the action (transcode), the resource (media file), and the possible transformations. It also distinguishes itself from sibling tools (which focus on subtitles, clipping, audio extraction, and merging) by being the general transcoding tool.

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 general media conversion but provides no explicit guidance on when to use this tool versus the siblings. It doesn't state prerequisites (e.g., input file must exist) or when not to use it. However, the sibling names offer some implicit differentiation.

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