get_friends_current_games

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

No annotations are provided, so the description carries all responsibility for behavioral disclosure. It states a read operation ('Get') but does not mention authentication requirements, rate limits, whether it requires a prior friend list, or any edge cases (e.g., private profiles). An agent gets no warnings or conditions beyond the bare action.

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, concise sentence that is front-loaded with the verb and resource. Every word contributes meaning; there is no wasteful filler. It is appropriately sized for such a simple tool.

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?

While the output schema covers return format, the description omits practical context such as dependencies on other tools (e.g., get_steam_friends) or authentication state. There are no parameters, but an agent would benefit from knowing that this tool only works when a Steam connection is established. Given the absence of annotations and the presence of a sibling ecosystem, the description is incomplete for a fully informed call.

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?

There are zero parameters, and the schema covers 100% (trivially), so the description does not need to compensate for missing parameter information. The baseline for zero-parameter tools is 4, and the description does not add conflicting details. No parameter explanations are necessary.

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 purpose: 'Get what games your Steam friends are currently playing.' It uses a specific verb (Get) and resource (games your Steam friends are currently playing), and it differentiates itself from sibling tools like get_steam_friends (which returns friends) and get_steam_library (which returns your own library).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a Steam friend list or authentication) or exclude any scenarios. An agent must infer usage context from the name and description alone, which is insufficient for selecting among many similar Steam tools.

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