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

Beyond the readOnly/idempotent annotations, it discloses the result ceiling (twelve candidates), what each result carries (score, genres, cast, runtime, links), that an authorized connection adds personal Rec Score predictions, and the distinction between chart attention, new releases, chart market and availability country. It also explains what trending/rising/popular actually measure and how chart_freshness/chart_age_days qualify the data.

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 triggering phrases are front-loaded and most sentences carry distinct information (chart semantics, freshness, market vs availability). A few clauses are marginal or redundant with the schema, such as enumerating every returned field and the trailing "No ReelRecs account required" repeat of the earlier no-questionnaire point.

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 a nested request object, five sibling alternatives and an output schema, the description covers routing, the providers/country pitfall, chart definitions and freshness. The enumerated return fields are mildly redundant with the output schema but do not leave any gap an agent needs before calling.

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?

Although reported schema coverage is 0%, the description supplies the key semantic traps: providers must be paired with constraints.country because country alone does not establish availability, genre/runtime/year/exclusion filters exist, and limit tops out at twelve. It does not explain variety, languages, offer_types, or the movie-vs-episode runtime split, so some nested parameters rely on the schema alone.

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 names a specific resource (U.S. audience charts) and a specific action (find current candidates, then judge fit for the viewer's mood), and opens with concrete triggering queries. It separates itself from recommend_titles/search_titles by stating no reference title or preference questionnaire is needed, so an agent can route correctly without opening the schema.

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 explicitly says when to use it ("Start here for 'Netflix tonight'...") and when-not ("not live sports fixtures or broadcast schedules"), and clarifies it needs no account or seed title. The "find candidates first, then judge their fit" instruction gives a clear workflow, and the exclusions point the agent elsewhere for other cases.

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