mdl_explore_top_movies

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds nothing on top of that: no indication of scope, pagination, ranking window, or what "top" is measured by, which is the main behavioral question for this tool.

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 short and front-loads the resource, which is good. But the second sentence is filler that adds no actionable information about the opaque params object, so the brevity reflects under-specification rather than efficiency.

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 an open-world, parameter-driven explore endpoint with no output schema and an undocumented free-form `params` object, the description is not sufficient for an agent to call it correctly or predict results. It omits what upstream parameters mean and what the result set represents.

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 0% for the single `params` parameter, and the description only says it is "a JSON object of upstream parameters" – a hand-wave that conveys no keys, types, or expected fields. It does not compensate for the coverage gap.

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?

"Explore: top movies" names a resource (top movies) and a generic verb (Explore), which weakly distinguishes it from siblings like mdl_explore_top_airing or mdl_explore_trending by content type. However, the verb is a label rather than a described action, and nothing states what is returned or how "top" is defined.

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 gives no guidance on when to use this tool versus the many adjacent explore/search siblings (mdl_explore_trending, mdl_explore_recommended, mdl_search_titles, etc.). The agent is left to infer selection purely from the name.

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