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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds that it records 'privacy-safe operational telemetry for reliability and aggregate usage measurement'—a behavioral disclosure beyond annotations. It also clarifies output limits (no transcript). No contradiction with annotations.

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 compact and front-loaded: purpose, returned artifact, exclusion, and telemetry in four short sentences with no filler. Every sentence contributes to agent understanding.

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?

An output schema exists, so return format is covered elsewhere. The description covers what it returns, what it doesn't, and side effects. A minor gap: it doesn't state behavior when both show and episode are omitted (since no parameters are required), which could be ambiguous for the agent.

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 description coverage is 100%, so the schema already documents all three parameters (show, episode, limit) with descriptions. The description only reiterates that filtering is by show and/or episode, adding no syntax or format detail beyond the 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 clearly states the verb 'Get' and the resource 'episode summary and key points', specifies how to select (by show name and/or episode title), and distinguishes itself by explicitly saying it does not return the full transcript. This separates it from siblings like search_moments or list_shows.

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?

It provides a clear negative usage guideline ('Does not return the full transcript') and states the tool returns a canonical episode-hub link. However, it does not name any sibling tools as alternatives for cases like full transcripts or latest episodes, leaving some routing to inference.

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