mdl_explore_top_airing

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds no behavioral context beyond that — no indication of result volume, freshness, pagination, or auth requirements.

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-loaded, which is appropriate, but the second sentence about 'upstream parameters' is vague jargon that consumes space without adding usable information. Size is fine; content density is low.

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 and a completely undocumented pass-through parameter, the description should at minimum explain what 'top airing' returns and what params are accepted. Neither is present, leaving the agent unable to invoke the tool meaningfully.

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% and the single 'params' property is an unconstrained anyOf object with additionalProperties=true. The note that it is 'a JSON object of upstream parameters' names the field but conveys no accepted keys, formats, or examples, so it fails to compensate for the opaque schema.

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 'Explore: top airing' essentially restates the tool name rather than explaining what it returns or how 'top airing' differs from siblings like mdl_explore_top_movies, mdl_explore_trending, or mdl_explore_upcoming. An agent gets no sense of the ranking source, time window, or result shape.

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 and no named alternative among the many explore_* siblings. The agent must guess whether this is the right discovery endpoint versus mdl_explore_top_movies or mdl_explore_currently_watching.

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