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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and scope are covered. The description adds some value with 'enriched' (hinting at augmented/derived fields) and the fact that the dataset id is fixed to the `steam-games` enum value, but it says nothing about return shape, pagination, or error behavior beyond what structured fields provide.

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 short sentences with zero waste; the core action and lookup key are front-loaded before the sibling routing advice.

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?

An output schema exists, so return values need not be described, and annotations cover the safety profile. For a single-record lookup with one fully-documented parameter, the description is nearly complete, missing only minor hints about output shape or failure modes.

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% and the single appid parameter is fully documented in the schema ('Steam app id, e.g. 570'). The description only restates 'by appid' and adds the fixed dataset id value, which is not a schema parameter. Baseline 3 is appropriate when the schema already carries the parameter semantics.

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?

States a specific verb and resource ('Returns one enriched Steam catalog record') with the lookup key ('by appid'), and explicitly names the sibling it is not (datasets_steam_games_search). An agent can distinguish this single-record fetch from the search tool without opening either schema.

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 routes the agent to datasets_steam_games_search for searching, which implies the when-to-use for this tool (fetch one known record). No explicit when-not or prerequisites, but the alternative is named clearly.

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