Найти серию

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

Annotations already declare readOnlyHint=true, so the read-only safety is covered. The description adds valuable non-obvious behavior: descriptions of episodes not yet reached are hidden by default, and only the existence of the episode is shown. This informs the agent about spoiler behavior without contradicting the 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 two short sentences with no filler. The first sentence states the core purpose, and the second front-loads the key behavioral caveat about hidden unwatched episode descriptions.

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?

Given the output schema, annotations, and moderate parameter count, the description covers the main operational concerns: tracked-series scope and spoiler defaults. It is slightly thin on search matching semantics, but the schema and annotations carry enough of the remaining burden.

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 descriptions cover query, show, and include_unwatched, while limit, season, and include_specials lack descriptions. The description adds meaning only to the unwatched/spoiler parameter by explaining the default hidden behavior. With 50% schema coverage, the description provides marginal but not complete compensation for the undocumented parameters.

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 states a specific action: search episodes by plot description among tracked series. This clearly distinguishes it from siblings such as show_search (searching shows), show_profile (show details), tracking_update (mutating tracking state), and watch_next (next episode).

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 description gives useful context: the search is scoped to tracked series and uses episode descriptions. However, it does not explicitly say when to choose this tool over siblings, nor does it mention any exclusions or alternative tools.

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