media_extract_thumbnails

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 lacks disclosure of behavioral traits such as file overwrite behavior, supported image formats, error handling, or permission requirements. For a tool that generates multiple files, these details are important.

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 main description sentence is concise and front-loaded, but the subsequent parameter listing duplicates schema information and could be removed. It is not overly verbose but could be more efficient.

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 that the tool has 4 parameters, 1 required, and an output schema, the description is minimal. It does not clarify what the tool returns (though an output schema exists), nor does it explain edge cases or constraints like maximum interval or allowed widths.

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%, meaning the description adds no additional meaning beyond parameter names and defaults. The listed parameters ('Path to video file', 'Seconds between thumbnails', etc.) merely restate the schema titles and provide no constraints or format details.

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 'Extract thumbnails at regular intervals (contact sheet / storyboard)', which is a specific verb and resource. It distinguishes from sibling tools like 'media_extract_thumbnail' (singular) and 'media_scene_detect' by emphasizing regular intervals.

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 creating contact sheets or storyboards but does not explicitly state when to use this tool versus alternatives like 'media_extract_thumbnail' (singular thumbnail) or 'media_scene_detect'. No exclusions or prerequisites are mentioned.

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