get_coming_soon

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

Annotations already declare read-only, idempotent, open-world behavior, so the description's job is to add operational context — and it does, stating the sort order ('soonest first'), the from_date default of today, and that cursor comes from a previous page. It doesn't discuss rate limits, page-size ceilings, or total-count behavior, so a 4 rather than 5.

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?

The single-sentence purpose statement is front-loaded and the Args block is terse, one line per parameter. The Args list partially restates schema field names, but each line still contributes semantics (allowed values, format, defaults) rather than pure repetition.

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 an output schema present, the description needn't explain return shape, and it correctly focuses on ordering, date defaults, and pagination chaining. What's missing is only marginal: whether results are limited to a window (e.g., theatrical only), and confirmation of default kind/limit values.

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%, so the description carries the full burden and largely meets it: it supplies the allowed values for kind ('movie or tv'), the YYYY-MM-DD format for from_date along with its today default, what limit counts (per page), and the chaining rule for cursor. Remaining gaps are minor — the default values for kind (movie) and limit (25) are only in the schema, not restated.

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 opening line 'Upcoming releases, soonest first' names a specific resource and its ordering, which is clearly distinct from query-oriented siblings like search_titles or advanced_title_search. It stops short of naming an alternative sibling explicitly, so it lands just below the top band.

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 implied by 'upcoming releases' and the from_date default of today, so an agent can infer this is the discovery tool for future titles. There is no explicit when-not guidance, no mention of how it differs from search_titles for a date-ranged query, and no prerequisites stated.

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