steam_queryWorkshop

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

No annotations are provided, and the description gives minimal behavioral context. It lacks details on rate limits, pagination behavior beyond the cursor parameter, or what happens when no results are found.

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 single concise sentence followed by a requirement note. It is front-loaded with the core purpose but could benefit from a slightly more structured breakdown.

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 that the tool has 6 parameters, no output schema, and no annotations, the description is too brief. It omits important context such as the structure of returned results, error handling, and pagination mechanics beyond the cursor parameter.

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%, so the baseline is 3. The description adds a high-level summary of filtering ('text, tags, and sort order') but does not provide additional meaning beyond the schema's per-parameter descriptions.

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 action ('Search and browse'), the resource ('Steam Workshop items'), and the scope ('for a given app'). It also mentions filtering capabilities, distinguishing it from sibling tools like steam_getWorkshopItem which retrieves a single item.

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?

The description mentions the prerequisite 'Requires STEAM_API_KEY', but provides no guidance on when to use this tool versus alternatives such as steam_getWorkshopItem for specific items or steam_searchApps for general app search.

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