pws_set_event_active

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

Despite destructiveHint=true in annotations, description adds crucial behavioral context: archiving is reversible, retains completed/cancelled show history, is blocked under specific conditions, and defaults to preview. This goes beyond the annotation and helps the agent understand the risk and preconditions.

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 sentences, front-loaded with action and BETA warning, and each sentence conveys essential usage and constraint information without unnecessary fluff.

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?

Description covers the key behavioral constraints and preview default, but with no output schema it leaves some ambiguity about what preview/confirmation returns or requires. However, it is adequate for understanding the tool's core function and preconditions.

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 description coverage is 0%; description only explains the preview parameter ('Defaults to preview') but does not explain active (true=restore, false=archive) or confirmed semantics. With low schema coverage, this is insufficient parameter guidance.

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 specifies a clear action (archive/restore with preview option) on a specific resource ('player-company event series'), distinguishing it from sibling tools like pws_create_event or pws_cancel_show. It also clarifies preview mode and the reversible, conditional nature of archiving.

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?

Provides clear context: defaults to preview, archiving is reversible and blocked while an unfinished non-cancelled show exists. Does not explicitly name alternatives or exclusions, but among siblings this is the only event-series archive/restore tool, making usage context reasonably clear.

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