steam_community_recommendations

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

No annotations provided. Description discloses that the upstream serves a fixed batch, is credential-free, and does not support tag filtering or deep pagination. Lacks info on rate limits, error handling, or data freshness.

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?

Single paragraph, 4 sentences, each adding value. Front-loaded with main purpose. No wasted words.

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?

Describes output structure (author, playtime, etc.) and limitations. No output schema, so description compensates well. Missing explicit batch size or pagination details, but sufficient for a feed tool.

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 coverage is 100% so the baseline is 3. The description adds context by grouping filters (e.g., 'review kind/sort') but does not significantly extend the schema's own 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 it fetches community-recommended reviews across the whole store, listing returned fields (author, playtime, etc.). This distinguishes it from siblings like steam_reviews which are per-app.

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?

Explicitly lists filter dimensions (review kind, playtime window, language, region) and notes limitations: no deep pagination, no tag filtering without auth. Context is clear but no explicit 'when to use vs alternatives' statement.

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