Hide or unhide games

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal a non-obvious side effect: the change applies account-wide across all devices. However, it does not explain dry_run behavior, return values, or failure modes, so the disclosure is only partially complete.

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?

Two short, front-loaded sentences communicate the action and the key side effect with no wasted words. The structure is highly scannable for an agent.

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 operation itself is simple and the account-wide effect is stated, which is valuable. But the tool has no output schema and no annotations, and the dry_run parameter is undocumented, leaving some gaps for an agent deciding how to invoke it safely.

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 schema already documents value and appids, but dry_run is left completely undescribed. With 67% schema coverage and no compensating description detail, the dry_run parameter remains ambiguous.

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 ('Hide games from the Steam library, or unhide them') and clearly communicates the bidirectional action. It is easy to distinguish from sibling tools like steam_set_favorite or steam_library_list.

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 relevant context by noting the change affects the library view on every device signed into the account, which is an important consideration. It does not explicitly name alternatives or provide when-not-to-use guidance, but no sibling tool performs the same hide/unhide function.

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