Remove games from a collection

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

With no annotations provided, the description carries the behavioral disclosure burden. It does disclose the key safety-relevant behavior: games remain in the library and only membership changes. However, it does not explain dry_run behavior, whether the operation is reversible, or what happens when removing the last game from a collection.

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 two short sentences with no filler. The action is front-loaded, and the clarifying behavioral caveat follows immediately, making it easy for an agent to parse.

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 is complete enough for a basic call, and the schema covers most parameters. But with no output schema and no annotations, the tool would benefit from explaining dry_run semantics and when to use id versus name to identify the collection.

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 75%, so the schema already documents id, name, and appids in detail. The description adds no parameter-level meaning and does not clarify the undocumented dry_run parameter. This is an adequate but not enhanced baseline.

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 states a specific verb ('Remove') and resource ('games from a static collection'), and the clarifying clause 'The games stay in the library; only the collection membership changes' distinguishes this from library deletion or uninstallation. It effectively differentiates from sibling tools like steam_uninstall_game and steam_collection_delete.

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 clearly conveys the action, but it does not explicitly say when to choose this tool over alternatives like steam_collection_add_games or steam_collection_replace_games. It implies usage for modifying collection membership but gives no exclusions or comparative guidance.

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