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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real value by disclosing the ranking metric (watch-through depth) and the 30-day lookback window. It omits the default result count and whether ordering is descending by that metric, which would complete the picture.

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?

A single front-loaded sentence that defines the resource, the ranking metric, the time window, and the optional filter with no filler. Every clause earns its place.

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?

With no output schema, the description should hint at what comes back; it conveys the ordering principle but not the shape of the results (fields per show, default page size). For a simple zero-required-param list tool this is adequate but leaves gaps an agent would notice on first call.

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 coverage is 50%: genre is fully documented in the schema with its enum, and the description's 'optionally for one genre' merely repeats it. The limit parameter has no description anywhere, and the description does not mention the 1-10 cap or a default, leaving half the parameter surface unexplained.

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 the resource (short dramas) and the exact ranking criterion: ranked by how far viewers watch, over a 30-day window. That is far more specific than a title restatement. It does not explicitly contrast itself with recommend_shows or search_shows, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the browse/discover entry point versus get_show (single item) and search_shows (query-driven), but the description never states when to pick this over recommend_shows. It does clarify the optional genre scoping, which is the only explicit guidance.

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