pws_schedule_show

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

The description adds behavioral context beyond the annotations by explaining the preview vs. actual scheduling distinction and noting persistence verification. The annotation destructiveHint=true is consistent with the scheduling behavior; no contradiction. However, it does not detail side effects or failure modes.

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, efficient sentence that conveys the core purpose and key behavioral nuance (preview vs. schedule). The 'BETA:' prefix and 'Verifies persistence' are useful but the latter is vague.

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?

This is a destructive, non-idempotent tool with six parameters and no output schema, yet the description is minimal. It omits parameter explanations, return-value expectations, and further context, making it under-specified for an AI agent.

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 description only hints at the venue parameter ('optionally at a validated venue') and the preview flag ('Defaults to preview'). It does not explain eventId, airDate, confirmed, or location, and with 0% schema description coverage, this leaves most parameters semantically opaque.

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 the specific action 'PREVIEW OR SCHEDULE' and clearly identifies the resource as 'a show instance for a player-company event series,' differentiating it from sibling tools like pws_plan_show or pws_cancel_show. It also notes optional venue validation, adding further specificity.

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 implies the tool is used to schedule or preview show instances, but it does not explicitly state when to use it over alternatives like pws_plan_show or pws_validate_show_plan. No exclusions or alternative tools are mentioned, leaving the usage largely implicit.

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