Get wishlist

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

Annotations already mark the tool as read-only, and the description goes beyond them by adding the keyless-access condition for public profiles and clarifying the returned data includes price and review info. This adds meaningful behavioral context without contradicting the 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 compact three-sentence definition, each sentence earning its place: what the tool returns, why it is useful, and a key access condition. It is front-loaded and free of filler.

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?

The tool is simple–two optional params, a read-only operation, and no nested objects or output schema required for invocation. The description provides the output shape and access context, making it effectively complete for agent selection and correct calling.

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 100%: both the user and limit parameters already have clear descriptions and defaults. The tool description gives no additional parameter-level semantics, so the baseline of 3 is appropriate.

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 states a specific verb and resource—'get' the player's Steam wishlist—and details the content: current price and review data for each entry. This distinguishes the tool from siblings like get_game_reviews and get_my_library, so an agent can identify it without inspecting schemas.

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 provides concrete use context: a wishlist is a stated-intent signal and is useful for spotting items on sale, and it notes that no key is needed when the profile is public. It does not explicitly state when not to use it or name alternative tools, so some selection guidance is left to the agent.

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