video_analyze

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

Adds context beyond annotations: uses Gemini structured output, strict contract pipeline details, and mentions quality gates and artifact rendering. No contradiction with idempotentHint=true.

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?

Four compact sentences with clear structure: main purpose, input constraints, core features, and optional advanced mode. No wasted words.

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?

Covers all key parameters and modes (instruction, output_schema, strict_contract, caching, thinking). Output schema and schema descriptions fill remaining gaps. Could briefly explain thinking_level but name is self-explanatory.

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?

Adds value beyond schema descriptions: mutual exclusivity constraint for url/file_path, purpose of output_schema, and strict_contract behavior. Schema already covers most details, so slightly above baseline.

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?

Clear verb+resource: 'Analyze a video' with specific input types (YouTube URL or local file). Distinguishes from sibling tools like video_metadata or video_batch_analyze by focusing on analysis with custom instructions.

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 states 'Provide exactly one of url or file_path' and explains strict_contract mode. Lacks explicit when-not-to-use or alternatives, but the context is clear.

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