Что включить

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds meaningful behavioral constraints beyond that: only released episodes are considered, only backlog items, and only episodes that fit the time limit. 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?

Two short, purposeful sentences: the first states the overall action, the second states the filtering rules. There is no filler, repetition, or unnecessary detail, 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?

For a simple read-only recommendation tool with three optional parameters and an output schema, the description provides enough to understand what the tool does and how it filters. It could be slightly richer with an explicit usage note, but nothing critical is missing for correct invocation.

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 67%, with minutes and include_new already documented. The tool description adds useful context for minutes ('укладываются в заданное время') and indirectly for include_new ('только вышедшие серии'), but it adds nothing about the limit parameter, which remains only defined by its schema constraints.

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 uses a specific action ('Выбрать, что посмотреть') and a clear resource ('из накопившегося'), then narrows the behavior with concrete criteria: only released episodes from the backlog and only those fitting the given time. This clearly distinguishes it from the sibling search, profile, and update tools.

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 intended use is implied by the phrasing: use it when the user wants a recommendation of what to watch now from their backlog within a time budget. However, the description does not explicitly name alternatives, state when not to use it, or contrast it with episode_search, show_search, or tracking_update.

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