search_saved_episodes

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

With no annotations provided, the description carries the full burden and does useful work: it discloses that this is a read-only GET operation, paged, and bounded rather than an unbounded native search. The phrase 'bounded walk + client-side filter' is informative, though somewhat jargon-heavy and it does not specify the exact boundary behavior.

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?

Extremely concise: one core sentence plus a compact quota/endpoint note. No filler or repetition of schema information, and the main purpose is front-loaded.

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?

Reasonably complete for a read-only search tool: the schema covers parameters and response_format hints at output style, while the description adds the key behavioral details of bounded walking, paging, and quota. It lacks an explicit output-shape description and alternative-tool guidance, but those gaps are not critical given the schema richness.

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 80%, and the schema already documents show, query, max_results, and response_format. The description adds mild context for scan_cap via 'bounded walk' but does not meaningfully elaborate parameter semantics beyond what the schema provides, so the baseline of 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?

States a specific verb and resource: 'Search saved episodes,' and the parenthetical 'bounded walk + client-side filter' distinguishes it from catalog-wide searches like search_episodes and unfiltered listings like get_saved_episodes. The tool's purpose is immediately identifiable.

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?

Implies usage through the phrase 'saved episodes,' making it clear this targets the user's library rather than the global catalog. However, it does not explicitly state when to prefer it over alternatives like search_episodes or get_saved_episodes, leaving the routing mostly to inference.

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