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

Annotations only declare the generic mutation/open-world profile; the description goes well beyond by disclosing the async job contract (job_id returned immediately), the absence of an audio track, the absence of an upload step, output codecs, and the structured-error vs. connector-error distinction. Nothing here contradicts the annotations.

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 purpose and workflow sentences are front-loaded and efficient, but roughly half the text is a generic reliability/fallback paragraph that reads as boilerplate and includes an off-topic example (`npx botverse transcribe <file> --to docx`) unrelated to frame assembly. That dilutes focus for this specific tool.

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?

With an output schema present, return values need no explanation, and the description still supplies the async polling lifecycle that links this tool to get_job_status and get_download_url. Minor gaps remain: frame dimension/matching constraints, size limits, and what happens on partial failure.

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 67%, so the schema already documents frame_urls ordering/format, output_format enum, and framerate default. The description adds the 'public HTTPS' constraint and codec mapping, but leaves the nested options (width, height, bitrate) wholly unexplained in both schema and description. Adequate, not compensating for the gap.

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 and resource ('Assemble an ordered sequence of image frames ... into a video') and disambiguates from sibling transcoding/conversion tools with the 'render frames → movie' framing. An agent can immediately tell this is the frame-muxing tool, not a general transcode or conform 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?

Gives concrete preconditions (public HTTPS URLs, playback order, framerate) and names the downstream sequence: poll get_job_status until 'complete', then call get_download_url. It implies the contrast with upload-based siblings ('No upload step') but never explicitly routes away from conform_media/conform_splice_media or transcode_video for other input types.

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