render_svg_to_video

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

No annotations are provided, so the description carries the full burden. It usefully consolidates that transparency is only supported for webm/gif/apng/mov, but says nothing about where the file is written by default, overwrite behavior, performance/rate characteristics, or failure modes. It adds some value but leaves meaningful behavioral gaps for a file-writing tool.

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 led by the verb 'Render', with zero filler. Every clause (input sources, output formats, transparency) adds information without repetition.

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 11 parameters, no output schema, and no annotations, the description is adequate on the core render operation and output formats but omits the return value (e.g., the output file path) and edge-case behavior such as bgColor/transparent conflicts or default format selection. Complete enough to attempt a call, but not to predict results confidently.

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%, so every parameter is already documented in the schema. The description's 'from file path or raw SVG code' phrasing restates the svgFilePath/svgContent distinction that the schema already provides, adding no new semantics. Baseline 3 applies.

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+resource: render an animated SVG into a video or animated image, and enumerates both input sources (file path or raw SVG) and output formats. It does not explicitly name or differentiate itself from the sibling inspect_svg_animation, but the render-vs-inspect distinction is inferable.

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 explains what the tool produces but gives no when-to-use guidance, no prerequisites, and no mention of the alternative inspect_svg_animation for pre-render inspection. An agent must infer the use case from the input/output description alone.

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