Get pending Steam installs and updates

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

The annotations declare readOnlyHint: true, and the description adds valuable context beyond that: it specifies the tool reads local manifests, does not force update checks, and snapshots states like paused downloads. This fully describes the tool's side-effect-free behavior.

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 two concise sentences. The first states the tool's action and target, the second clarifies its scope. Every word serves a purpose 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?

Given the moderate complexity (3 optional parameters, no output schema), the description covers the tool's behavior and constraints well, but it does not explain what the tool returns (e.g., list of game names or IDs). Since there is no output schema, the description should hint at the response format for completeness.

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 0%, and the description does not explain the three parameters (limit, offset, include_idle). While limit and offset are common pagination parameters, include_idle is not self-explanatory. The description must compensate for the low schema coverage but fails to add any parameter meaning.

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 specifies the verb 'list' and the resource 'games whose local Steam manifests show an install, update, download, or paused-download state'. It distinguishes itself from siblings like 'steam_client_status' and 'steam_get_game_install_status' by focusing specifically on download/update status from local manifests.

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 states it is a local snapshot and does not force Steam to check for new updates, which clearly implies appropriate usage contexts (e.g., checking current status without triggering network activity). However, it does not explicitly mention when not to use this tool or suggest alternatives among the listed siblings.

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