edit_video

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

With no annotations, the description carries full burden. It mentions supported editing operations but fails to disclose critical behavioral traits such as whether edits are destructive (overwrite original) or create a new version, permissions required, or impact on existing data. The description is vague about side effects.

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 extremely concise: two sentences that cover the core functionality and list supported options. No wasted words, front-loaded with the main verb 'Edit a video'.

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 the tool's complexity (2 params, nested object, no output schema, no annotations), the description is minimal. It covers the main operations but misses important context like return value, error handling, or prerequisites (e.g., video must exist). Adequate for a simple tool but incomplete for production use.

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?

Input schema coverage is 100% with detailed property descriptions. The description summarizes the editing options but adds no additional meaning beyond what is already in the schema. For a high-coverage schema, baseline is 3, and the description does not exceed that.

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 it edits a video by adding clips or trimming sections, and lists specific operations like trimming start/end, extracting clips, and updating metadata. While it differentiates from siblings (get_video, list_recorded_videos) by being an edit operation, it does not explicitly distinguish from merge_videos, but the verb 'edit' implies single video modification.

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 provides a clear purpose but lacks explicit guidance on when to use this tool versus alternatives like merge_videos. It implies usage for editing a single video, but does not state when not to use it or mention prerequisites. The context hints from sibling names partially compensate, but no direct comparison.

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