Search the Steam catalog

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

Annotations already indicate readOnlyHint=true, and the description adds useful behavioral context: it is keyless, returns full details per hit, and performs no personalised ranking. These traits go beyond what annotations alone convey, though it does not discuss rate limits or pagination.

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 short sentences with zero filler. The core action is front-loaded, the usage guidance follows immediately, and the keyless note is a single efficient word.

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 description covers the tool's purpose, key differentiator, and auth requirement, which is strong for a search tool with rich schema documentation. Without an output schema, it only vaguely characterizes the return payload as 'full details', but this is a minor gap given the clear purpose.

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 88%, so the schema already documents most parameters thoroughly. The description adds little about specific parameters beyond the general notion of 'structured filters', so the baseline of 3 applies.

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?

States a specific verb ('Search the Steam store'), the mechanism ('structured filters'), and what is returned ('full details for each hit'). It explicitly distinguishes itself from recommend_games by noting the lack of personalised ranking, making sibling differentiation clear.

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?

Gives an explicit usage condition ('when you want raw discovery without any personalised ranking') and names the preferred alternative ('recommend_games is usually the better starting point'). This is direct guidance an agent can act on without requiring inference.

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