steam_getLeaderboardsForGame

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

No annotations are provided, so the description carries full burden. It discloses the API key requirement and that no publisher access is needed, but does not mention rate limits, pagination, or error handling. For a simple list operation, this is adequate but could be enhanced.

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: first states purpose and output fields, second states prerequisites. No wasted words. Front-loaded with key information.

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 one-parameter list tool, the description covers purpose, output details (IDs, names, sort methods), and prerequisites (API key). No output schema, but description compensates. Complete for the complexity level.

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 has 100% coverage: one parameter with description 'Steam application ID to list leaderboards for'. The description repeats this without adding extra meaning beyond 'appid'. Baseline 3 is appropriate.

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 a specific verb ('list'), resource ('all leaderboards for a Steam app'), and outputs ('numeric IDs, names, and sort methods'). It distinguishes from sibling tools like steam_getLeaderboardEntries which get entries for a specific leaderboard.

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 mentions the prerequisite (Steam Web API key) and access level ('No publisher access needed'), but does not explicitly state when to use this tool versus alternatives or provide exclusions. Usage is implied but not guided.

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