video_create

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

With no annotations, the description discloses the core behavior (generating an mp4 from session photos) but omits details such as output location, failure behavior, or side effects on source data. It adds useful context about accepting a session name or folder path.

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 two tight sentences with the action front-loaded and the parameter note on its own line. No filler or redundancy.

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?

It covers the tool's purpose and the key session input, and the output schema handles return-value documentation. However, it lacks guidance on optional parameters (fps/width) and expected side effects, leaving some ambiguity for a tool with no annotations.

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 explains the critical `session` parameter (session name from `timelapse_list` or folder path) but gives no meaning for `fps` or `width`, which have 0% schema coverage. Since the schema only supplies names/types/defaults, the description does not compensate for the majority of parameters.

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 clear action ('generate') and specific output ('timelapse video mp4') from 'a session's sequence of photos', which differentiates it from sibling capture/control tools. It also references `timelapse_list` for valid session names.

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?

It provides clear context that `session` should be a name from `timelapse_list` or a folder path, establishing a prerequisite. However, it does not explicitly name alternatives or state when not to use this tool.

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