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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: it is regenerated daily (not real-time), is an interactive card in compatible hosts, and contains the same data as the homepage hero. This supplements the annotations well.

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 sentences and covers the essential purpose, content structure, and interactive nature. It is somewhat detailed but not overly verbose; however, some phrases like '(importance-scored major event, or a deterministic prime-time film fallback)' could be more concise.

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 no parameters and the presence of an output schema, the description adequately explains the tool's output composition (main decision, vertical picks, stats). It does not cover edge cases or error scenarios, but those are minor for this read-only tool.

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?

There are no parameters, so the baseline is 4. The description does not need to add parameter meaning since the schema is fully covered and empty.

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 it is a 'what is worth watching tonight?' card with specific content (main decision, picks per vertical, measured stats) and mentions it is a visual card in MCP Apps. However, it does not explicitly differentiate from siblings like tv_recommend_today, though it notes it shares data with the homepage hero.

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 implies it is for getting a curated nightly overview, but it does not provide explicit when-to-use or when-not-to-use guidance compared to sibling tools. No exclusions or alternatives are mentioned.

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