image_stylize_reel

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

No annotations are present, so the description carries the full burden. It does not explain that the tool reads input_path and writes output_path, whether it overwrites existing output, what formats are supported, or what post-cleanup and remove_orphans actually do.

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; the parenthetical style list is long but useful. It is appropriately concise, though slightly unstructured due to the embedded enumeration.

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?

For an eight-parameter mutation tool with no annotations, no output schema, and 0% schema description coverage, the description leaves too much unspecified for reliable invocation.

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 0%, so the description must compensate for eight parameters. It names the style enum values and alludes to cleanup and outlines, but factor, upscale, input_path, output_path, outline_mode, outline_color, and remove_orphans remain semantically unexplained.

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 ('Applies') and resource ('procedural Reel visual styles'), with example style names. The styling purpose is clear, though it does not explicitly differentiate itself from siblings like image_convert or image_showcase.

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 no guidance on when to choose this tool over alternatives such as image_convert or palette_tool, and provides no prerequisites, exclusions, or when-not-to-use information.

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