pws_dissolve_stable

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

Annotations already declare destructiveHint=true and readOnlyHint=false, but the description adds context: 'BETA' signals instability, 'VERIFIES deletion' indicates the tool confirms the action, and 'Defaults to preview' explains a safer default behavior. This goes beyond annotation basics, though it does not detail irreversible consequences beyond 'permanently dissolve.'

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 sentence that is front-loaded with the core action and key qualifiers (preview, permanent, verifies, default). No redundant words; every part contributes value.

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 essential behavior but omits important context: it does not explain what a preview returns, how 'verified deletion' is reported, or the precise roles of preview and confirmed. With no output schema, these gaps are noticeable, though the tool is relatively simple.

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%, so the description must explain parameters. It only mentions 'Defaults to preview,' which gives minimal meaning to the preview boolean, but leaves stableId and confirmed unexplained. The interaction between preview and confirmed is ambiguous, making the parameter semantics insufficient.

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 and resource: 'PREVIEW OR PERMANENTLY DISSOLVE a player-company stable.' This clearly distinguishes it from sibling tools like pws_create_stable (creation) and pws_get_stables (listing), leaving no ambiguity about its function.

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 usage when a stable needs to be dissolved, and no sibling tool covers this operation. However, it lacks explicit guidance on choosing between preview and permanent modes, and does not mention alternatives or when not to use the tool.

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