Get a player's wishlist

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

Discloses important behaviors: works without key if public, returns found:false in private cases, items have no names, and need separate tool for details. Adds value beyond readOnlyHint and openWorldHint 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?

Three sentences, front-loaded with main purpose, no filler. Every sentence provides essential information.

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 one optional parameter and no output schema, the description covers input, conditions, output format (list of appids, found:false), and missing name details. References necessary sibling tools.

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?

Adds meaning beyond the schema: describes that omitting steamid uses server-configured ID, and instructs to convert vanity names first. Schema coverage is 100% and description enriches it.

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?

Clearly states the tool lists appids on a player's wishlist sorted by priority, using SteamID64. Distinguishes from siblings by specifying the unique resource and sorting behavior.

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 tells when to use (for wishlist data), when not to expect results (if private, returns found:false), and provides alternatives: use get_game for names, resolve_vanity_url for vanity names.

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