Batch store card for many games

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

Annotations indicate readOnlyHint and openWorldHint. Description adds behavioral context: 'keyless call', efficient batch, and specific return fields including steam_deck enum values. No contradictions.

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, zero waste. Key benefits and functionality front-loaded. Efficient and clear.

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, but description explains return fields (price, discount, review %, release date, steam_deck). Additional context: keyless, efficient, and source of appids. Complete for this tool's complexity.

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% (all three parameters described). Description adds meaning by explaining appids usage, that country/language override environment variables, and the return value context (steam_deck field). Compensates beyond baseline.

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?

Description uses specific verb 'Get' and resource 'batch store card for many games'. Clearly states it retrieves price, discount, review %, Steam Deck compatibility, and release date for a list of appids. Distinguishes from sibling tools by emphasizing batch operation over per-game calls.

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 states this is the efficient way to check a wishlist or library, avoiding per-game requests. Provides source of appids: search_games, get_wishlist, get_owned_games. No when-not-to-use stated but context is clear.

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