thumbnail

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about writing an image file to `output`, what image format results, or what `overwrite=false` does when the target exists. 'High-quality frame' hints at internal quality selection but is never explained, and failure modes for out-of-range timestamps are unstated.

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 well-formed sentence that front-loads the action and embeds the timestamp format inline, with no filler. It is efficient, though the brevity comes at the cost of the missing parameter and behavior detail noted elsewhere.

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?

An output schema exists, so return values need not be explained, but for a five-parameter media tool with zero schema coverage and no annotations, the description leaves the agent without enough to call it correctly. It should at minimum explain input/output file semantics, the width parameter, and overwrite behavior.

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%, and the description only clarifies one of five parameters: `at` with its HH:MM:SS format. The semantics of `input`, `output`, `width` (does null mean native resolution?), and `overwrite` are left entirely undocumented in both schema and description.

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 states a specific verb and resource: grab a single high-quality frame from a video at a given timestamp. That clearly separates it from siblings like transcode_video or extract_audio, though it never explicitly names those alternatives or clarifies how it differs from extract_stream.

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?

There is no guidance on when to use this versus convert_image, extract_stream, or probe_media, and no mention of prerequisites such as supported container formats or whether the timestamp must be within the video duration. The agent must infer usage entirely from the tool name.

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