Plan Steam Game Night

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

The description adds behavioral context beyond annotations by specifying that it retrieves online status and co-op/multiplayer metadata. Annotations already indicate read-only and idempotent, so the description complements them without contradiction.

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, well-structured sentence that efficiently conveys the tool's purpose and output. No unnecessary 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?

Despite having an output schema and no required parameters, the description lacks details on how to use the five parameters effectively. It does not explain constraints like 'selected or currently visible friends' or how 'limit' and 'maxFriends' interact. Incomplete for a tool with 0% parameter documentation.

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%, so the description must explain parameters, but it does not. It does not clarify how parameters like 'friendNames', 'friendSteamIds', or 'minFriendsOwning' affect results. The description is too vague to compensate for missing schema descriptions.

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 tool finds games shared with friends, including online status and co-op/multiplayer metadata. The verb 'find' and resource 'games shared with friends' are specific, and the tool is distinct from siblings like steam_discover_games or steam_search_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 implies use for planning a game night but does not explicitly state when to use this tool over alternatives or exclude other cases. No 'when-not-to-use' or alternative tool mentions.

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