get_steam_app_details

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

No annotations provided, so the description carries full behavioral disclosure burden. It only states 'Get store details' but omits rate limits, authentication needs, edge cases (e.g., invalid appid), or return format. The read-only nature is implied but not explicitly stated.

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 sentence that is concise and front-loaded with the action ('Get store details'). Every word is functional; no wasted content.

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 lists example data fields but does not specify the output format (e.g., JSON structure). Without an output schema, users must infer the response shape. It is adequate for a simple tool but lacks completeness regarding what exactly is returned.

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% with parameter descriptions for appid, cc, and l. The tool description adds no additional meaning beyond the schema; it neither explains the parameters further nor provides examples of expected values beyond what schema already says.

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 gets store details for a Steam app, listing specific data types (game info, price, platforms, Metacritic score). It implicitly distinguishes from sibling tools like get_steam_achievements or search_steam_store by focusing on a single app's store page.

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?

No explicit guidance on when to use this tool versus siblings (e.g., search_steam_store for searching, get_steam_achievements for achievements). The description implies it's for a specific app's store details but lacks when-not-to-use or alternative cues.

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