Get current discounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds useful context beyond annotations: scoped to the Steam store front page, returns discount percentage and original/final price, and requires no API key. This is meaningful extra behavioral disclosure.

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, front-loaded with the core purpose, followed by a targeted alternative pointer and an auth note. Every sentence adds value, no fluff or repetition.

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 the tool's simple list behavior, the output schema, and annotations, the description sufficiently covers scope, return content, auth requirements, and the key sibling alternative. Nothing important is missing for an agent to select and invoke this correctly.

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?

Input schema covers both parameters (country, language) with descriptions, giving 100% coverage. The description doesn't add parameter-specific details but doesn't need to since the schema already explains overrides. Baseline of 3 is appropriate when schema carries the weight.

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 uses a specific verb ('List') and identifies the exact resource ('games currently on special on the Steam store front page'). It clearly distinguishes itself from the sibling discover_games by contrasting front-page-only scope with the all-catalog alternative.

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?

Explicitly provides when-to-use context: front-page specials. Names discover_games with min_discount as the alternative for broader catalog discounts, giving clear exclusion and direction. Also notes no API key required, reducing usage friction.

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