get_library

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

The description discloses that the tool returns playtime and last-played date for each game, which is helpful. However, with no annotations provided, it lacks details on authentication requirements, rate limits, or whether the tool requires user authorization. The behavior is partially transparent.

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 a single sentence of 13 words, front-loaded with the main action and resource. Every word is informative with no redundancy or extraneous content.

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 simple tool with one optional parameter and no output schema, the description adequately covers what the tool returns. It could mention authentication needs, but overall it is sufficiently complete given the low complexity.

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?

The schema already provides a description for the lone parameter (include_unplayed) with 100% coverage. The tool description does not add additional meaning about the parameter beyond what the schema offers, so a baseline score of 3 is appropriate.

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 states the verb 'Get', the resource 'full Steam game library', and specifies the returned data (playtime and last-played date). It effectively distinguishes from siblings like get_game_details (specific game) and get_recently_played (subset).

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 implies usage when the full library is needed, but it does not explicitly state when to use this tool versus alternatives, such as get_recently_played for recently played games or search_library for filtered queries. No exclusions or prerequisites are mentioned.

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