Get a collection and its games

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

No annotations are provided, so the description carries the disclosure burden. It does state pagination, and 'Return' implies a read-only operation, but it does not specify error behavior, id/name precedence, or how include_games=false changes the result.

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 terse sentences with no filler. The core action is front-loaded, and the pagination note is the only additional behavior disclosed, earning its place.

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?

Adequate for a simple fetch when combined with the schema, but with no output schema and no annotations, an agent still lacks return-shape cues and edge-case behavior. The description does not clarify what happens when both id and name are supplied or when include_games is false.

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 description coverage is 80%, with good inline descriptions for id, name, limit, and offset. The description adds little beyond hinting at 'with its games' for include_games, so it does not meaningfully compensate for the undocumented include_games parameter.

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 uses a concrete verb ('Return') and identifies the resource ('one collection with its games'). 'One' helps distinguish this from steam_collections_list, though it does not name the sibling explicitly.

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 intended use is implied: fetch a single collection by ID or name. However, there is no explicit guidance about when to prefer this over collections_list or how to handle the id/name alternatives.

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