Coming soon (on-sale radar)

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

Annotations already declare read-only, non-destructive behavior. The description adds useful behavioral context: the 48-hour threshold, sorting by first night, a configurable horizon, and the extra metadata in detailed mode. No contradiction with annotations.

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 tight sentences communicate the core behavior, the booking use case, configurability, and detailed-mode metadata without repetition. The most important scope information is front-loaded.

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 a read-only listing tool with two optional parameters and an output schema, this description is complete. It covers what is returned, how it is sorted, the time threshold, and optional response details, so an agent can confidently invoke it.

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 100%, so the baseline is 3. The description adds value by explaining what the horizon is for and what "detailed" mode includes, such as confidence level, source tier, reporting sources, and verified_at.

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 clearly identifies the resource: films whose first SF screening is more than 48 hours out, sorted by first night. It also frames the tool as an "on-sale radar" for early booking, which distinguishes it from siblings like scenef_whats_playing and scenef_now.

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 a clear use case: identify upcoming runs worth booking early. It implies when to choose this tool over current-screening tools, though it does not explicitly name alternatives or state when not to use it.

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