steam_find_friends_who_own

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful context about friend-library scope but does not disclose behavioral traits like concurrent owned-games lookups, limits, or response shape. No contradiction with annotations.

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, front-loaded sentence: verb, resource, and scope are all present. 'not store search' earns its place by preventing confusion with sibling tools.

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?

Combined with the output schema and annotations, the description sufficiently covers purpose, friend-library scope, and the play-now variant. It does not explain what happens when steamid is omitted, but that behavior is documented in the schema.

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% at the top level, and the description does not compensate by listing parameters. It only hints at appid via 'specific game' and omits limit, steamid, max_friends, playing_now, and response_format. The nested schema has good descriptions, but the description itself adds little parameter meaning.

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 has a specific verb ('List') and resource ('which of a user's friends own (or are playing) a specific game'). The parenthetical 'not store search' explicitly distinguishes it from store-search siblings like steam_search_apps.

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?

It gives a clear use case ('who can I play X with') and an explicit scope exclusion ('not store search'). It does not name sibling alternatives such as steam_get_friend_list or steam_compare_players, so it misses the highest bar for guidance.

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