set_steam_client

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

No annotations provided, so description carries full burden. It only says 'switch', implying a state change, but fails to disclose side effects, required permissions, or whether the switch is immediate or queued. Substantially insufficient.

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 short sentence but omits critical information given the tool's complexity. It is not appropriately scaled; the cost of brevity is too high.

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?

With no annotations, 0% schema coverage, 9 parameters, and an output schema not leveraged, the description is completely inadequate. The agent cannot safely or correctly invoke this tool based on the current definition.

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 0%, but the description adds no explanation for any of the 9 parameters (3 required). The agent lacks any insight into what 'target', 'gameid', 'mode', etc. mean or how they interact.

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 it switches the Steam client mode for the main session, providing a verb and resource. However, it lacks specificity and does not differentiate from sibling tools like set_session or steam_frame properties. The term 'mode' is vague.

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?

No guidance on when to use this tool versus alternatives, no prerequisites or exclusions. The description is purely declarative with no context for decision-making.

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