steam_package

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

No annotations are provided, so the description carries the burden. It mentions credential-free public access, which is useful, but lacks details on rate limits, error handling, or what happens if the package does not exist.

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?

Two sentences, no waste. The first sentence establishes purpose and output fields; the second adds parameter context and authentication info. Efficiently structured and front-loaded.

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 fetch tool with 3 parameters and no output schema, the description covers the core purpose, parameter semantics, and authentication. It lacks behavioral details like caching or error responses, but remains adequate for typical 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 coverage is 100%, and the description adds value by explaining that 'cc' controls region/currency and that 'packageid' is numeric. This enriches the parameter understanding beyond the schema alone.

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?

Description clearly states it gets Steam store details for a package and lists the specific returned fields (name, apps, price, platforms, release date). The phrase 'a purchasable bundle' effectively distinguishes it from sibling tools like steam_app which handles individual games.

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?

Description explains that 'cc' selects store region and price currency, and notes it is credential-free. While it implies use for packages versus apps, it does not explicitly contrast with adjacent tools like steam_app or steam_items.

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