Search transcripts

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

Annotations include readOnlyHint=true, so the tool's safety profile is already known. The description adds value by clarifying the scope of search (titles, participants, tags, speakers, spoken text). However, it does not disclose result format, ordering, or pagination behavior, leaving some behavioral aspects unexplained.

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 a single, concise sentence that directly states the tool's purpose and searchable fields. No wasted words, and the important information is front-loaded.

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 tool is relatively simple with two parameters and a read-only annotation, but there is no output schema. The description does not mention what the search returns (e.g., matching transcript IDs, snippets), which leaves some ambiguity for an agent. For a search tool, clarifying the output would make it more complete.

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?

The schema covers query with a case-insensitive description and limit with numeric constraints. The description adds semantic meaning to query by specifying the fields it applies to, but says nothing about limit's behavior. With schema description coverage at 50%, the description partially compensates but does not fully clarify both parameters.

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's function: 'Search titles, participants, tags, speakers, and spoken transcript text.' It uses a specific verb (search) and resource (transcripts), and enumerates the searchable fields, which distinguishes it from sibling tools like list_transcripts and get_transcript.

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 implies usage for finding transcripts through search but does not explicitly state when to use this tool versus siblings or provide exclusions or alternative guidance. The verb 'Search' gives context, but no detailed usage instructions are provided.

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