mdl_search_top_dramas

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: no result count, ranking basis, pagination, or freshness of the "top" list, which are the traits an agent would actually need.

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?

It is a single short fragment with no wasted words and is front-loaded. However, the brevity reflects under-specification rather than disciplined concision, so it earns only a middling score.

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 parameters, no output schema, and no annotations explaining the return shape, the description is the only place an agent could learn what this returns (list size, ranking criterion, ordering). It supplies none of that, leaving the tool's output behavior opaque.

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?

The tool takes zero parameters, so there is nothing for the description to clarify; the baseline of 4 applies. Schema coverage is 100% and the empty argument object is self-explanatory.

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?

"Search: top dramas" is essentially a restatement of the tool name (mdl_search_top_dramas) with no added specificity. It does not say what "top" means (ranked by popularity, rating, recency?), nor does it distinguish itself from siblings such as mdl_explore_top_movies, mdl_explore_top_airing, or mdl_search_titles.

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?

There is no when-to-use guidance whatsoever. The sibling list contains several overlapping candidates (mdl_search_titles, mdl_explore_top_movies, mdl_explore_top_airing, mdl_explore_trending), and the description gives the agent no basis for choosing this one over them.

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