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

No annotations are provided, so the description carries the full behavioral burden. It says it generates commands and HTML syntax, implying it does not execute ffmpeg itself, but it does not state output format, validation behavior, side effects, permissions, or whether any files are read or written.

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?

A single front-loaded sentence with no filler. It is concise, though extremely terse given the tool's parameter complexity.

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 has 6 undocumented parameters, no annotations, and no output schema. The description omits parameter meanings, output format, and usage details, making it inadequate for correct invocation without opening the schema.

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?

There are 6 parameters with 0% schema description coverage, so the description must compensate. It mentions codecs and 'poster', but none of the actual parameters (fps, audio, input, width, output, quality) are explained or mapped to meaning.

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?

States a specific verb (產生/generate) and resource (ffmpeg 指令, HTML video 語法) for web background video compression, naming supported codecs (H.264, VP9, AV1, poster). This clearly distinguishes it from unrelated sibling tools.

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 through '網頁背景影片壓縮', giving context for when the tool is useful. However, it offers no explicit when-not conditions or alternative tools, and no prerequisites or input requirements are stated.

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