steam_get_featured_specials

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds context about 'currently ON SALE' (temporal freshness) and 'featured specials', but does not disclose other behaviors like default limit, response format, or regional pricing nuances beyond what the schema provides.

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, concise sentence that immediately states the purpose. It contains no filler, is well-structured, and is easy to parse. It earns its place with zero unnecessary words.

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 simplicity, strong annotations (read-only, idempotent), and presence of an output schema that defines return values, the description is sufficient. It covers the core purpose and scope. Minor omissions like default response format or regional pricing details are already available in the schema, so the description remains complete for typical use.

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 description does not explain parameters, and schema description coverage is 0% from the description's perspective. However, the input schema itself provides clear descriptions for limit, country_code, and response_format, so the agent can understand parameters from the schema. The description adds no additional meaning, but the schema compensates, hence a baseline score.

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 uses a specific verb ('List'), specifies the resource ('games currently ON SALE (featured specials)'), and scopes it to the Steam store. This clearly differentiates it from siblings like steam_get_store_highlights or steam_discover by emphasizing the 'ON SALE' filter.

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 clear context about its purpose (listing games on sale) but does not explicitly mention alternatives or exclusions. While the context is understandable, there is no direct guidance on when not to use this tool compared to similar store-related tools.

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