video_analysis

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

No annotations are provided, so the description carries the burden. It discloses file size limit and format support, but does not explain frame-sampling behavior (maxFrames, fps) or output format. Behavioral traits beyond basic constraints are missing.

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 sentences, efficiently front-loaded with the core purpose and constraints. No wasted words; every part adds value.

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?

The description covers the main purpose and file constraints, but given 4 parameters and no output schema, it omits explanation of frame-sampling parameters (maxFrames, fps) and how the analysis produces output. It is adequate but not fully informative.

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 100%, so baseline is 3. The description adds the file size constraint (≤8MB) beyond the schema, but does not elaborate on prompt usage or the frame-sampling mode. Minimal additional meaning is provided.

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 the verb (inspect), resource (videos), and scope (describe scenes, detect events, answer questions). It specifies supported formats and file size limit, distinguishing from image-focused sibling tools like image_analysis.

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 implies usage for video analysis but does not provide explicit guidance on when to use this tool versus alternatives (e.g., image_analysis for static images). No exclusions or when-not-to-use context is given.

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