steam_app

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

The description explicitly states it is 'Credential-free public Steam storefront JSON', disclosing authentication requirements and output format. No annotations exist, so this is sufficient for a read-only tool.

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 sentences, front-loaded with the main action, no extraneous information. Every sentence serves a purpose.

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 return fields and parameter usage. Without an output schema, explaining the returned metadata fields is helpful. It lacks error handling details, but overall is adequate for a simple 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%, but the description adds meaningful context: cc selects region/currency, l selects language, filters shrinks payload with comma-separated fields. This adds value beyond the schema's minimal 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 retrieves Steam store details for a single app, listing specific metadata fields (title, type, price, etc.). This distinguishes it from sibling tools like steam_reviews or steam_achievements by focusing on store metadata.

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 implies usage for obtaining store metadata but does not explicitly provide when-to-use guidance or contrast with alternatives like steam_steamspy or steam_search. The agent must infer from context.

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