get-transcript

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

No annotations are provided, so the description must disclose behavioral traits. It states the tool returns 'full transcript with timestamps' but does not mention error handling, rate limits, or what happens if a transcript is unavailable. A basic retrieval tool is expected, but the lack of edge-case information with no annotations makes this only adequate.

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 sentences, no verbose or redundant phrasing. Front-loaded with the main purpose, followed by concise details on URL acceptance and output. Every sentence 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 has 3 parameters and no output schema, the description covers the basic 'what' but is vague on output format and error scenarios. It does not explain timestamps format or how to handle missing transcripts. It is minimally adequate for a simple tool but not fully informative.

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 coverage is 100%, so the baseline is 3. The description adds minimal extra beyond the schema: it reinforces URL format flexibility and implies the default inclusion of timestamps, but does not provide significant new meaning for each parameter.

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 verb 'Retrieve' and the resource 'transcript of a YouTube video', and distinguishes itself from the sibling tool 'get-transcript-languages' by focusing on obtaining the actual transcript text. It also specifies handling various URL formats and returning timestamps, making the purpose very specific.

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 when to use this tool (to get a transcript) but does not explicitly mention the sibling tool 'get-transcript-languages' or when to prefer it. The context is clear for the core usage, but no exclusion or alternative guidance is provided.

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