search_video_moments

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

The description adds context beyond annotations (e.g., API used, return format with timestamps and metadata). Annotations already declare readOnlyHint=true and idempotentHint=true, so the description's behavioral disclosure is adequate and consistent.

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 concise with three sentences: one on what it does, one on how it works, and one on when to use it. No wasted words; front-loaded with the core purpose.

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 is complete for a read-only search tool: it explains inputs, semantic search capability, and output structure (timestamps, metadata). Without an output schema, it sufficiently covers return values, though more detail on response fields could improve completeness.

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% with detailed descriptions for both parameters. The description adds value by explaining the prefix convention for collection_id and providing example queries, enhancing understanding beyond the schema alone.

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 performs 'AI-powered semantic search to find specific video segments,' using specific verb+resource, and the examples distinguish it from siblings like search_video_summaries by focusing on precise moments across speech, text, and visual content.

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 explicit use cases like 'needle-in-haystack spoken and visual content, specific discussions, or thematic analysis,' but does not explicitly mention when to avoid using it or alternatives among siblings.

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