analyze_video

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

No annotations provided; description carries full burden. Covers automatic backend selection, caching, frame budget cap, and that frame_interval is ignored by Gemini. No contradictions.

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?

About 120 words, front-loaded purpose, clear sectioning for each parameter. No fluff, every sentence 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?

Given output schema exists, description needn't detail return values. Covers inputs, parameters, caching, backend, and force_refresh. Complete for a tool with 4 params.

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 description must compensate. It explains each parameter: url/file_path are mutually exclusive, frame_interval possible values and behavior, force_refresh bypasses cache. Adds significant meaning beyond schema.

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?

Clearly states verb 'analyze', resource 'video', and outputs 'frames + transcript + metadata'. Differentiates from siblings like extract_frames_at and get_video_transcript_only by being comprehensive.

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?

Explicitly requires exactly one source (file_path or url), provides guidance on frame_interval values, and mentions caching and force_refresh. Does not explicitly contrast with siblings but context implies this is the all-in-one tool.

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