Open Steam's uninstall wizard

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

With no annotations, the description carries the full burden and does a superb job: it discloses the non-silent dialog behavior, the irreversible deletion, save-file consequences, and the Steam Cloud exception. It even calls out the confirm requirement, going well beyond minimal safety warnings.

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?

Four crisp sentences, front-loaded with the core action and using the rest for essential warnings. Every sentence earns its place with no filler.

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 destructive tool with no annotations and no output schema, the description covers action, interaction model, irreversibility, save implications, and the confirmation contract. dry_run is already explained in the schema, so nothing necessary for correct invocation is missing.

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 already documents confirm and dry_run with descriptions, and the description only repeats the confirm=true requirement without adding new detail. appid is left without added meaning, though 'for a game' loosely ties it to the tool's purpose. With 67% schema coverage, the description adds only marginal parameter value.

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 ('Open') and resource ('uninstall wizard for a game'), and the 'NOT silent' note immediately clarifies that this does not perform a hidden uninstall. It clearly distinguishes itself from the sibling steam_install_game by naming the uninstall direction.

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 gives clear context: use this to uninstall a game, with an explicit caveat that it is not silent and opens a manual dialog. It does not name an alternative or state an explicit when-not-to-use, but the context is sufficient for an agent to select it appropriately.

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