Get Steam Wishlist

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

Mentions reliance on an undocumented service and Store metadata endpoints, implying potential instability. However, with no annotations, it does not fully disclose side effects, authentication needs, or rate limits.

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?

Single sentence is concise, but it omits essential details. It earns its place but could benefit from additional context without becoming verbose.

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 4 undocumented parameters, no annotations, and an output schema, the description is insufficient. It lacks parameter details, usage context, and behavioral transparency.

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%, and the description provides no explanation of parameters (limit, steamid, unreleasedOnly, maxMetadataApps). This fails to add meaning beyond the raw 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 retrieves a Steam wishlist and specifies the use of an undocumented wishlist service. It distinguishes from siblings like 'steam_check_wishlist_updates' but could define 'get' more precisely.

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?

No guidance on when to use this tool versus alternatives such as 'steam_check_wishlist_updates' or 'steam_get_owned_games'. The description lacks context for optimal usage.

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