Create the whole video (one-shot, autonomous)

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

Discloses autonomous one-shot execution, background job, and that no user confirmation is needed. Annotations (readOnlyHint false, idempotentHint false) align; description adds behavioral detail beyond 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?

Front-loaded with key phrase 'ONE-SHOT builder — the preferred path,' but is somewhat lengthy with repeated context. Still organized well with flow steps. Minor redundancy (e.g., 'content_json = ...') could be trimmed.

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?

No output schema, but description informs about polling project_status for mp4 path and QA frames, and finishing with write_publish_meta. Covers typical workflow and essential details for a complex tool. Could be more explicit about error handling.

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?

Adds context beyond schema: content_json must include meta/scenes with voiceover and language-specific note, images must match paths, slug kebab-case. Schema already has descriptions, so description enhances but is not fully compensating for low coverage (80% is high).

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?

Description clearly states it is a one-shot builder that scaffolds, downloads, writes content, and renders in one job. It distinguishes from siblings by being the preferred path and specifying typical flow after image gathering.

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?

Explicitly says when to use (after storyboard and images chosen, typical flow with search_wikimedia_images), and provides instructions: run autonomously, do not pause to ask user, then poll project_status and use write_publish_meta.

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