search_transcript

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 that it returns only timestamped snippets ('Returns timestamped snippets only'), which is useful. However, it does not mention permissions, read-only nature, pagination, or error behavior. The description adds some but not extensive behavioral context.

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 two short sentences, front-loaded with the main action. The first sentence states the purpose, and the second gives context. No waste; every word 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?

Given the tool's simplicity and the presence of an output schema, the description is adequate for basic use. However, it does not explain important parameters like 'url' and 'lang', and it assumes the reader knows what 'cues' are. The completeness is minimal but not severely lacking.

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 the description must compensate. It explicitly references 'query' but does not explain the 'url' or 'lang' parameters. It provides no additional meaning beyond the schema, leaving two of three parameters undocumented in both schema and description.

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 tool 'finds cues matching a query' and returns 'timestamped snippets only', identifying both the action and the resource. It differentiates from siblings like get_transcript and get_segment by focusing on search and targeted retrieval.

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 provides explicit guidance: 'Use for long videos: locate the relevant moments without loading everything.' This implies when to use the tool and contrasts with loading a full transcript, though it does not explicitly name alternatives. The context is clear enough for an agent to select this tool appropriately.

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