search_transcript

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

Discloses read-only behavior (searches existing content), case-insensitive matching, and context window. No annotations provided, so description carries full burden. Could mention it does not modify the transcript.

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?

Well-structured with a clear purpose statement, important caveat, sample prompts, and parameter blocks. Every sentence is informative and economical.

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?

Fully explains purpose, prerequisites (transcribe_video), usage flow (leading to extract_video_clip), and parameter details. Output schema existence means return values are covered elsewhere.

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?

All four parameters are explained with context: url links to transcribe_video, query is case-insensitive, model_size must match, context_segments defaults to 2. Schema had 0% coverage, so description adds significant value.

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 searches an existing transcript for keyword matches, explicitly distinguishes itself from transcribe_video, and provides sample prompts for clarity.

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 when to use (search existing transcript) and when not (does not transcribe), and directs to transcribe_video as prerequisite. Sample prompts reinforce correct usage.

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