Get Steam library and playtime

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

Annotations already indicate read-only behavior. The description adds that it requires specific environment variables and uses the optional Steam Web API, providing useful context. However, it does not disclose filtering behavior or effects of missing keys.

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 concise with two sentences, front-loading the purpose and following with prerequisites. No wasted words, but could include more structure for a tool with multiple parameters.

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 6 parameters (all optional, unfiltered in description) and no output schema, the description is too sparse. It lacks details on return format, filtering logic, and error handling, making it incomplete for effective usage.

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 has 6 parameters with 0% description coverage, and the tool description provides no parameter explanations. The description does not compensate for the lacking schema descriptions, leaving parameter semantics entirely implicit.

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 verb 'Get' and resource 'the user's complete Steam library, playtime, and last-played data' clearly state the tool's function. It distinguishes from siblings like steam_client_status and steam_find_game, though 'complete' slightly conflicts with filtering parameters.

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 mentions required keys (STEAM_API_KEY, STEAM_ID) and web API nature, providing context. However, it does not specify when to use this tool over siblings or when not to use it (e.g., if no API key), limiting guidance.

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