steam_set_favoriteAdd or remove Steam games from the Favorites collection by appid and boolean flag. Resolve game names to appids with steam_library_search before calling this tool.
Add games to, or remove them from, Steam's Favorites collection.
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | true to favorite, false to un-favorite. | |
| appids | Yes | Steam appids. Use steam_library_search to resolve names to appids first. | |
| dry_run | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It does state that the tool can both add and remove favorites, but it omits important behavioral details such as permissions, side effects, reversibility, dry_run behavior, and what the response looks like. For a mutation tool, this is a significant gap.
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 a single, front-loaded sentence with no redundant content. It efficiently communicates the core operation without wasting words.
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 state-changing tool with no annotations and no output schema, the description is too thin. It does not explain dry_run semantics, when to prefer this over other sibling tools, or what error or return behavior to expect, leaving an agent without enough context for safe invocation.
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 appids and value, but the description adds no additional meaning for them. More importantly, the dry_run parameter is not described in either the schema or the description, and the description does not compensate for this gap.
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 action ('Add games to, or remove them from') and the specific resource ('Steam's Favorites collection'). This distinguishes it well from sibling tools like steam_set_hidden or the collection management tools, whose purposes are different.
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: it is clearly about managing the Favorites collection. However, it does not explicitly say when to use this tool versus alternatives like collections or hidden flags, nor does it provide any exclusion guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.