steam_category

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

With no annotations, the description covers key behavioral aspects: it uses Steam's keyless IStoreQueryService (credential-free), lists the response fields, explains slug case-insensitivity, and mentions default relevance ordering. It could be more explicit about pagination behavior, but overall provides significant transparency.

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 4 sentences, front-loaded with the main action, and each sentence adds unique value. It is fairly concise, though could be slightly more compact without losing information.

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?

No output schema is provided, so the description compensates by describing the return fields (WEIGHTED community tags, review-score, developer/publisher, etc.). It mentions pagination implicitly ('catalog slice') and ordering. For an 8-parameter tool, this is reasonably complete, though error conditions and response format are omitted.

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 schema covers all parameters with descriptions (100% coverage). The description adds value beyond the schema by explaining the slug parameter in detail (numeric id or name, case- and separator-insensitive, id resolution). This exceeds the baseline of 3 for high schema coverage.

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's purpose: 'Browse a store category (tag) with weighted community tags.' It specifies that it returns a catalog slice with detailed fields, and distinguishes itself from sibling tools like steam_tags by noting that for sorted or faceted browsing one should use /steam/tags.

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 explicitly tells when to use this tool vs alternatives: 'for sorted or os/price-faceted browse use /steam/tags' and 'resolve ids via /steam/tags/list.' It also notes that it is credential-free, helping agents decide on authorization needs.

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