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

With no annotations, the description carries the full burden. It discloses the primary behavior (retrieval of specific episode components) and adds value by explaining what 'full' includes. However, it omits any mention of authentication, response format, error behavior, or potential rate limits, leaving gaps for an agent.

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, well-structured sentence that front-loads the core action ('Get full episode data in one call') and directly lists contents. Every word is purposeful, with no fluff or repetition.

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 description is sufficient for a simple get tool with a single parameter: it states what the tool does and what data it returns. No output schema exists, but the listed components give a clear expectation. Minor gaps remain (e.g., whether transcript is included), but overall it is well-complete for the tool's complexity.

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 input schema already provides 100% coverage with a clear description for episode_id ('Episode ID'). The tool description adds no additional parameter-level detail, so it meets the baseline of 3 for high schema coverage.

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: 'Get full episode data in one call' with a specific list of included data (details, summary, quotes, asset mentions). It distinguishes itself from sibling tools like get_episode_details and get_episode_quotes by aggregating multiple data types.

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 phrase 'in one call' suggests using this tool when you need all the listed data at once, implicitly contrasting with the need for multiple calls to other tools. It provides clear context but does not explicitly mention alternatives or when not to use it.

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