Get a player's followed games

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is clear. The description adds important behavioral details: privacy constraint (found:false), capping at 200 items, and limited return fields. No 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 dense but well-organized: main purpose first, then details on privacy, return format, and usage flow. Slightly verbose but every sentence adds value. Could be slightly more concise but effective.

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?

Given the output schema exists, the description adequately covers privacy, limits, and integration with other tools. It explains the tool's role within the broader set of Steam endpoints, making it complete for an agent to use correctly.

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 already covers the sole parameter with 100% coverage. The description adds context: optional steamid, fallback to server config, and vanity URL conversion step. This provides value beyond the schema.

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 lists games a player follows on Steam store by SteamID64, distinguishes it from the wishlist, and specifies it returns appids and store_url capped at 200. It contrasts with sibling tools like get_wishlist.

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?

Provides explicit when to use (list followed games), with alternative steps: convert vanity name with resolve_vanity_url first, and pass appids to get_items for pricing. Warns about privacy (returns found:false if profile not public).

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