Search inside a video

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

Annotations already cover read-only/idempotent safety. The description adds useful behavioral detail beyond annotations: it returns per-result timestamps as clickable links to the exact second. It does not mention edge cases like missing transcripts or multiple language matches, so not a 5.

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, no filler; the core behavior is front-loaded and the usage note follows. Every clause earns its place.

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 plus schema and annotations give enough to call correctly: required inputs are clear, output shape is stated (timestamp links), and safety is covered by annotations. Without an output schema, slightly more detail on result behavior would be ideal, but nothing critical is missing.

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 covers 3 of 4 parameters (75%) with descriptions; the description mainly reinforces query and video concepts ('phrase', 'video') without adding syntax or defaults. The language parameter is left undocumented, but with high schema coverage, baseline 3 is appropriate.

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 opens with a specific verb and resource ('Find every place a phrase is said in a video') and states the concrete deliverable ('timestamps, each as a link that jumps to that second'). This makes it easy to distinguish from get_transcript and search_videos without inspecting schemas.

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?

It explicitly names the alternative class ('pulling a whole transcript') and the condition that selects this tool ('when you only need to locate something'). This is a clear when-to-use statement with an implied when-not-to-use.

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