datasets_steam_achievements_search

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

With no annotations, the description is responsible for behavioral disclosure. It covers pagination (page * page_size <= 10000) and data model, but does not mention read-only nature, rate limits, or error handling. The provided information is adequate but not comprehensive.

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 long, no waste. It front-loads the purpose, then explains the data model, and finally provides usage guidance. 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?

Given no output schema and simple parameters, the description sufficiently explains what data is returned, how to filter, and sorting. It could optionally mention default page and page_size behavior, but the schema covers those. Overall complete for the tool's complexity.

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 schema covers parameters with descriptions, and the description adds value by clarifying the sort enum meanings (`percent_desc`, `percent_asc`, `rank_asc`) and explaining that `app_id` filters to a specific game's achievements. This goes beyond the schema's minimal labels.

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 searches the steam-achievements dataset and specifies that it returns per-game global achievement unlock percentages with one document per appid × achievement. This distinguishes it from sibling steam dataset tools like steam_charts_search or steam_games_search.

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 explains how to use the tool (pass `app_id` to list a game's achievements) and describes the sort enum with defaults, but does not explicitly mention when to avoid using it or compare to alternatives. This is still clear for most use cases.

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