clip_frame

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

With no annotations, the description carries the load, and it does disclose the output form ('Returns the file path') and that extraction is read-only in effect. However, it omits permission requirements, behavior when `clip` is empty, and whether the frame is written to disk or streamed.

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?

Two short sentences, front-loaded with the action and the key parameter, with the return value noted briefly. Nothing wasted.

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 explaining return values is optional, yet the description does so succinctly. The gap is that odd parameter defaults (t=5, clip='', name='eufy_cam1') and the meaning of an unset clip are never addressed for a tool with 0% schema description coverage.

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 coverage is 0%, so the description must compensate for 3 undocumented params. It only clarifies `t` (seconds); `clip` and `name` (default 'eufy_cam1') are left entirely unexplained, including what an empty-string clip default means.

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 and resource: 'Extract one JPEG frame at `t` seconds into a motion clip.' The 'motion clip' scoping implicitly separates it from snapshot_camera (live capture), but no sibling is named explicitly. Clear purpose, weak sibling differentiation.

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?

No guidance on when to use this versus snapshot_camera or motion_clips. The phrase 'into a motion clip' hints that a clip reference is needed, but no prerequisites, exclusions, or alternative-routing statement is given.

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