Get an SGU episode

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

The description discloses internal data sources and behavior: 'Combines the RSS feed (recent metadata + audio) with the transcript wiki (segments + details).' This is fully transparent despite no annotations, and there is no contradiction.

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 sentences with no waste: first sentence defines purpose and contents, second sentence explains data sources and provides guidance on an alternative tool. Front-loaded and efficient.

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?

For a single-parameter tool with no output schema, the description is fully complete: it specifies input, output contents, internal behavior, and when to use a sibling. No gaps.

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 only parameter, episode_number, is already described in the schema (100% coverage). The description adds 'by number' but no additional meaning beyond schema. Baseline 3 is appropriate.

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 starts with a specific verb+resource 'Get a structured overview of one episode by number' and lists the included fields, clearly distinguishing the tool from its siblings, such as 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?

Explicitly states when to use this tool vs. an alternative: 'Use get_transcript for the full text.' This provides clear guidance on which tool to choose based on desired output.

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