pws_set_show_venue

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

Annotations already provide destructiveHint=true, but the description adds valuable behavioral context: it 'Validates the venue and verifies persistence' and 'Defaults to preview'—implying the default mode is non-destructive. It does not, however, explain the role of the 'confirmed' parameter in the actual mutation, which keeps it from being fully transparent.

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 three short sentences, front-loaded with the primary action, and each sentence adds unique information: what it does, validation/persistence, and default behavior. There is no wasted wording.

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 covers the core purpose and preview default, but omits the semantics of the 'confirmed' parameter, any indication of return values, and the side effects of actually setting the venue. Given there is no output schema, these are meaningful gaps for an agent using the tool.

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?

With schema description coverage at 0% and 5 parameters, the description must compensate, but it only explains the preview default and the event-default option. It leaves 'confirmed' completely unexplained and gives no additional meaning for 'showId' and 'venueId' beyond their names.

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 states the tool's function: 'PREVIEW OR SET the venue for an unfinished player-company show'. The verb 'SET' and resource 'venue' are specific, and the context 'unfinished player-company show' distinguishes it from sibling tools like pws_schedule_show or pws_create_event.

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 ('for an unfinished player-company show') and notes an optional mode ('optionally making it the recurring event series default'). However, it does not explicitly mention when not to use this tool or name alternative tools, so it stops 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.