get_featured_games

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns games split into two categories, with on-sale items including discounts and prices. This sufficiently conveys the read-only, non-destructive nature and output structure, though it could explicitly state no authentication needed or rate limits.

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 at two sentences, no wasted words, and front-loaded with the primary action. Every sentence adds value, meeting the highest standard for conciseness.

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 no parameters, no output schema, and no annotations, the description fairly completely explains what the tool returns. It specifies the two categories and mentions discounts/prices for on-sale items. However, it lacks details on the output format (e.g., list of IDs or names) or possible empty results, which would enhance 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?

The tool has zero parameters, so schema coverage is automatically 100%. The description does not need to add parameter semantics. The baseline for no parameters is 4, and the description adds no contradictory or missing information.

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's purpose: 'Get currently featured and on-sale games on Steam.' It specifies the resource (featured and on-sale games) and the verb (get), and elaborates on the output split into on-sale and regular titles. This distinctively sets it apart from sibling tools like get_game_details or search_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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention when not to use it, nor does it compare to siblings like get_featured_categories or search_games. The agent is left to infer usage context from the name alone.

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