render_html_video

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

With no annotations, description fully discloses behavior: frame-by-frame capture, quality preservation, color correction, codec details, resolution/fps range, output format (absolute path), and required dependencies (Playwright, ffmpeg). No contradictions.

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?

Well-structured single paragraph with clear segments: purpose, usage, behavior details, and requirements. Slightly verbose in listing quality claims, but overall concise and front-loaded.

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?

Covers core behavior, prerequisites, and output format. Parameter details are not explained, but schema provides defaults. With no output schema, description notes return path. Adequate for a tool with 6 params and dependencies.

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 0%, so description should compensate. It mentions output formats (mp4/gif/webm) which correspond to the 'format' parameter, but does not explain other parameters beyond what schema provides. Baseline 3 is appropriate as schema has defaults and types.

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?

Clearly states verb 'render' and resource 'HTML document' to video formats. Distinguishes from sibling tools like analyze_video by focusing on export of animated HTML pages.

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 'Use this to export a self-contained animated HTML page as a shareable clip.' Provides clear usage context but does not mention when not to use or alternatives among siblings.

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