steam_get_genres

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

With no annotations available, the description carries the full burden. It transparently indicates this is a read-only list-returning tool. It does not describe output format or ordering, but for a zero-parameter discovery list, those are minor omissions rather than significant behavioral gaps.

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?

A single, tightly written sentence conveys the action, the resource, and the intended purpose without wasted words. It is front-loaded and easy for an agent to parse quickly.

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 the zero-parameter schema, no annotations, and no output schema, the description is sufficiently complete: it states what the tool returns ('a list of common Steam genres and categories') and for what purpose ('discovery'). No additional context is necessary for correct invocation.

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?

The tool has zero parameters, so there is nothing meaningful for the description to add beyond the schema. The baseline of 4 applies because schema coverage is complete and no parameter documentation is needed.

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 a specific action ('Get a list') and a specific resource ('common Steam genres and categories for discovery'). It is distinct from sibling tools like steam_search_game or steam_get_details, which target search and game metadata rather than genre discovery.

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 phrase 'for discovery' provides a clear use case, and there is no competing sibling tool that retrieves genres/categories. It does not explicitly state when not to use it, but the uniqueness of the tool makes the intended usage reasonably obvious.

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