steam_get_dlc_list

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

With no annotations, the description carries the burden of behavioral disclosure. It conveys that this is a read/list operation and specifies exactly what is returned: App ID and name for each DLC. It stops short of detailing edge cases like invalid App IDs or pagination, but for a simple list retrieval this is adequate.

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?

The description is one clean sentence that front-loads the action, scopes it to a specific game, and includes the return contract. Every word earns its place with no redundancy.

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?

For a single-parameter tool with no output schema, the description is fully sufficient: it explains the purpose, the input, and the shape of the result. Nothing critical is missing for an agent to decide whether to call it and what to expect.

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 100%: the single parameter appid is already described as 'The Steam App ID of the main game'. The tool description adds little beyond that, so the schema does the heavy lifting and the baseline of 3 applies.

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 specific verb ('Get') with a specific resource ('list of all available DLCs') and clearly identifies the required input ('Steam game by its App ID'). It also states the return payload (App ID and name for each DLC), which distinguishes it from siblings like steam_search_game or steam_get_details.

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 description makes it clear that the tool is for retrieving DLC for a specific Steam game via App ID, which implies when it should be used. It does not explicitly name alternatives, but no sibling tool targets DLC lists, so the usage context is clear and exclusions are unnecessary.

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