video_export_frames

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

Without annotations, the description explains basic behavior (export frames, auto-generate output dir) and parameter defaults, but lacks details on file naming, overwrite behavior, performance impact, or non-destructive nature.

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 description is concise with a clear docstring format, using bulleted args to present parameter details without extraneous information.

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?

Given moderate complexity, 0% schema coverage, and presence of an output schema, the description sufficiently explains all parameters and usage, making the tool fully usable.

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?

The description adds full meaning to all 4 parameters, including path requirements, default values, format options, and auto-generation of output_dir, compensating for the 0% schema description coverage.

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?

The description clearly states 'Export frames from a video as individual images,' with a specific verb and resource, distinguishing it from the sibling tool 'video_extract_frame' which exports a single frame.

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 implies usage for extracting frames at a given FPS, but it does not provide explicit guidance on when to use this tool versus alternatives like 'video_extract_frame' or conditions in which it is not suitable.

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