Get a player's wishlist

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

Annotations declare readOnlyHint=true and openWorldHint=true, but description adds key context: no key needed, public vs. private behavior, items carry no names (use get_game), and default behavior when steamid omitted. No contradictions.

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?

Three sentences, first sentence front-loads main purpose. Every sentence adds value: returns condition, naming limitation, and prerequisite. No wasted 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?

For a tool with one optional parameter and no output schema, description fully covers return behavior (found:false), need for secondary tool (get_game), prerequisite (resolve_vanity_url), and default parameter behavior. Complete and self-contained.

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?

Input schema covers parameter with pattern and description. Description adds meaning: 'Omit to use the STEAM_ID configured on the server' and 'Convert a vanity name...first.' This provides default behavior and prerequisite info beyond 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?

Description clearly states 'List the appids on a player's Steam wishlist (sorted by their priority) by SteamID64.' The verb 'List' and resource 'appids on a wishlist' are specific, and the tool is distinct from siblings like get_owned_games or get_recently_played.

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?

Explicitly states when to use: 'Works without a key, but only if that player's wishlist/profile is public — otherwise it returns found:false.' Also gives alternative guidance: 'Convert a vanity name with resolve_vanity_url first.'

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