Get SGU transcript text

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

Describes the 'cleaned' nature and length warning. Explains section behavior (case-insensitive substring). No annotations, so burden is higher. Missing details on return format or potential errors.

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 concise sentences. First states purpose, second details optional parameter and prerequisite. No wasted words.

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?

Covers main functionality and parameter use. Lacks output schema description (no mention of return format). For a simple tool without output schema, mostly complete but could include what the response looks like.

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%, baseline 3. Description adds meaningful context: full transcript can be long, section is case-insensitive substring. Adds value beyond schema but not extensive.

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?

Clearly states it retrieves cleaned transcript text for an episode. Specifies optional section filter. Distinguishes from siblings by noting to use get_episode first for segment outline.

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?

Provides context on when to use the section parameter and recommends using get_episode first. However, does not explicitly mention when not to use this tool or compare with search_transcripts.

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