steam_getAppDetails

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

The description notes 'No API key required', which is a behavioral detail. However, without annotations, it does not disclose other relevant behaviors (e.g., read-only, rate limits, or data freshness). The description is adequate but incomplete.

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?

Two sentences: one specifying purpose and data types, another noting no API key requirement. No redundant information, efficient and front-loaded.

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 data types but does not explain the return format or structure. Given the complexity of Steam store data and no output schema, more detail on the response would improve completeness. However, the description is adequate for basic use.

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 input schema already covers all three parameters with clear descriptions (appid, cc, l). The description does not add semantic value beyond the schema, so a baseline score of 3 is appropriate.

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 retrieves Steam store data including specific types (price, description, reviews, tags, platforms, system requirements), distinguishing it from sibling tools that focus on subsets (e.g., steam_getReviews, steam_getPriceOverview).

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 guidance on when to use this comprehensive tool versus the more specific sibling tools (e.g., steam_getReviews, steam_getPriceOverview). No exclusions or alternatives are mentioned.

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