mdl_explore_upcoming

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The only added signal is the implication that 'params' is a passthrough of upstream parameters, which hints at a proxy wrapper but does not explain scoping, filtering, or what data is returned.

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?

Two short fragments with no waste, but the brevity reflects under-specification rather than tight editing. Nothing useful is front-loaded because nothing substantive is said.

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, 0% parameter documentation, and no meaningful behavioral detail, an agent cannot tell what this tool returns or what to pass in params. Only the generic annotations keep this from being a total void.

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 0% and the schema is just an opaque object with additionalProperties=true. The description says only that params is 'a JSON object of upstream parameters', which does not identify a single valid key, format, or expected value, so it fails to 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?

The description 'Explore: upcoming' merely restates the tool name and never says what is being explored or what 'upcoming' refers to (episodes, movies, air dates). It gives no basis for distinguishing this from siblings like mdl_explore_trending, mdl_explore_top_airing, or mdl_explore_currently_watching.

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 guidance on when to use this tool versus the five other mdl_explore_* siblings. No prerequisites, no context, no exclusions are stated anywhere in the description.

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