video_seek_frame

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

No annotations are provided, so the description carries the full behavioral burden, but it only hints that this is a frame-accurate conversion. It does not disclose side effects, authorization needs, error behavior, or how the nullable frame/seconds parameters interact.

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 definition is very short, but it is under-specified rather than concise. The cryptic "(TE.9)" reference adds no usable meaning for tool selection or invocation.

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 described, but the input and behavioral context are almost entirely missing. With no annotations and no parameter descriptions, an agent cannot confidently invoke this tool correctly.

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 the three undocumented parameters. It names none of them and does not explain fps, frame, seconds, or their defaults and nullable/mutually exclusive behavior.

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?

"Frame-accurate seek conversion" largely restates the tool name and adds only the modifier "frame-accurate"; it does not say whether the tool converts frame numbers to seconds, seeks a player, or returns a converted value. It also does not distinguish this tool from siblings such as video_extract_frame or video_inspect_temporal.

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 gives no when-to-use guidance, no prerequisites, and no alternatives. It does not indicate whether this is a preprocessing conversion step, a query, or an edit operation.

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