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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior. The description adds valuable context beyond that: it enumerates the summary's returned sections and states the output is markdown with a citable page URL, which matters since there is no output schema.

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?

One front-loaded sentence that names the resource, the output format, and the returned sections with zero filler. Every clause carries information the agent can use.

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-param, read-only fetch, the description plus full schema coverage plus annotations cover everything needed. It compensates for the missing output schema by describing the summary structure and the citation URL.

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% and already documents that the parameter accepts a UUID or a yedapo.com episode URL with UUID extraction. The description adds no parameter-specific guidance beyond what the schema provides, so baseline 3 applies.

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?

Specific verb and resource ('Get one episode's full Yedapo summary') plus the exact deliverable format (markdown, teaser, verdict, takeaways with timestamps, chapters, page URL). The 'one episode' scope naturally separates it from the sibling search_episodes listing tool.

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?

Usage is only implied – it fetches a single episode's summary, so an agent can infer it should call this when it already has an episode identifier. There is no explicit when/when-not guidance or reference to search_episodes for discovery.

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