get_library

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

With no annotations provided, the description carries the full burden. It mentions the output includes playtime statistics and suggests behavioral capabilities (sorting, filtering), but it does not disclose default behavior, authentication requirements, pagination, or whether the operation is read-only. The description is not misleading but lacks deeper context.

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 three sentences, front-loaded with the primary purpose, followed by concise usage examples. No fluff or repetition; every sentence earns 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?

The description provides a functional understanding but lacks details about default sort order, response format, and edge cases. For a tool with 4 optional parameters and no output schema, more clarity on defaults and return structure would improve completeness. It is adequate for basic use but not comprehensive.

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%, so the description must compensate. It adds meaning for two parameters: sort ('recent' as current obsessions) and filter ('unplayed' as backlog). However, it does not explain limit, steam_id, or the remaining enum values (playtime, name, all, played), leaving significant gaps for the agent.

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 tool retrieves the user's owned Steam library with playtime statistics, using a specific verb and resource. It distinguishes itself from siblings like get_recently_played and get_wishlist by focusing on owned games and playtime, covering both inventory and backlog use cases.

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?

It explicitly states when to use the tool: to understand ownership, identify backlog, and check playtime. It also provides specific sorting/filtering guidance ('Sort by recent', 'Filter unplayed'). However, it does not explicitly name alternative tools or state when not to use it, though the use cases imply a clear context.

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