upcoming_shows

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

There are no annotations to indicate side effects (e.g., read-only), and the description does not disclose any behavioral details beyond listing shows. Since the description carries the full burden without annotations, it lacks transparency about whether this operation modifies data or has other side effects.

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 description is a single sentence, extremely concise, and front-loaded with the core purpose. Every word serves a functional role, with no redundant phrasing or filler. It is appropriately sized for the tool's simplicity.

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?

The description provides basic scope (upcoming shows with dates on/after today) but lacks essential context, particularly the meaning of the include_related parameter. While output format is not required (schema exists), the missing parameter explanation leaves a significant gap for an agent to correctly invoke the tool with the desired behavior.

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?

The only parameter, include_related, is not explained in the description or schema. Schema coverage for parameters is 0%, and the description fails to compensate by defining what 'related' means or how this boolean affects results. The agent is left guessing at its purpose.

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 tool's function: listing shows that have been announced and that occur on or after today. It distinguishes itself from sibling tools like search_shows (searching), random_show (random selection), and latest_show (most recent).

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 context is implied rather than explicit. The description suggests it is for upcoming shows, but it does not explicitly state when to prefer this tool over alternatives like latest_show or search_shows. No clear 'use this when' or 'use that instead' guidance is provided.

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