Clear cached Steam data

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly describes what is deleted and, importantly, what is preserved: Steam files are untouched and collection backups are preserved, which is valuable safety context. It does not discuss reversibility or post-clear system effects, though the core destructive behavior is clear.

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 compact and front-loaded: the first sentence states the core operation, and the second adds meaningful exclusions. There is no filler or redundant restating of the title.

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 simple two-parameter tool with no output schema, the description plus schema is mostly sufficient to make a correct call. However, it does not connect to related cache operations like steam_cache_status or steam_cache_refresh, and it omits any note about the default scope behavior, so some practical context 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 description adds no parameter-level meaning beyond the schema. The dry_run parameter has a schema description, but the scope enum, including values like 'store-details' and 'store-reviews', is left entirely to the enum names, and the description does not explain how the default 'all' scope behaves.

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 names a specific action ('Delete') and resource ('this server's cached data') and further draws a clear boundary by stating Steam's own files are never touched and collection backups are preserved. This clearly differentiates it from status/refresh/library-related sibling tools.

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 no guidance about when to use this tool instead of steam_cache_status for inspecting cache or steam_cache_refresh for rebuilding it. There are no explicit conditions, prerequisites, or alternative tool mentions.

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