pws_get_upcoming_shows

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

Annotations already indicate a safe read operation. The description adds behavioral context by specifying the filtering criteria ('upcoming', 'unfinished') and the included fields ('duration and booking progress'), which is useful beyond what annotations provide. It does not contradict 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?

A single, clear sentence that is front-loaded with the action and resource. No wasted words.

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 simple list tool with annotations and a minimal schema, the description covers the key aspects: what is listed, for whom, and what is included in the result. The absence of an output schema is mitigated by mentioning the output fields. However, it could be more explicit about the limit parameter's effect, which still appears only in schema.

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 schema has one parameter (limit) with well-defined constraints, but the description does not mention or explain it. Since schema description coverage is 0%, the description should have compensated, but it does not, leaving the agent to infer the parameter's role from the schema alone.

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 uses a specific verb ('List') with a clear resource ('upcoming unfinished shows') and context ('for the player promotion'), and mentions output attributes ('duration and booking progress'). This distinguishes it from sibling tools like pws_get_show which retrieves a single show.

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 provides clear context that this is for listing upcoming unfinished shows in the player promotion, implying use when you need an overview. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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