steam_get_player_bans

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which conveys the safety profile. The description adds the specific ban categories (VAC, game, community, economy) but does not disclose additional behavioral traits like rate limits, authentication, or output format. It does not contradict annotations.

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 sentence that front-loads the action (Get) and immediately specifies the resource (ban status). No unnecessary words, and it communicates the essential purpose efficiently.

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 simple read-only tool with strong annotations and a well-documented input schema, the description is sufficient. An output schema exists, so return values are handled elsewhere. The description covers the key domain-specific detail (types of bans) and the rest is provided by structured metadata.

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 provides no parameter-level information, but the input schema includes detailed descriptions for steamid (SteamID64, vanity, or profile URL) and response_format (markdown/json). The schema covers the parameters effectively, so the description adds limited value beyond what the schema already provides.

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 specifies the verb 'Get' and the resource 'VAC / game / community / economy ban status' for a user. This distinguishes it from sibling tools like steam_get_player_summary or steam_get_player_badges. It is explicit and unambiguous.

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 makes the tool's purpose clear but does not explicitly state when to use it versus alternatives or any when-not conditions. However, among sibling tools none overlap with ban status, so the context is implicitly clear. No alternatives or exclusions are mentioned, so it misses a 5.

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