get_player_bans

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

No annotations provided. The description discloses that it returns multiple ban types, which is useful. However, it does not mention authentication needs, rate limits, or whether the operation is read-only. Given the simple retrieval nature, the disclosure is adequate but could be more thorough.

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?

Four sentences, each with clear purpose. First sentence states the function, second lists return types, third explains the parameter. No wasted 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?

For a single-parameter optional tool, the description covers the return value types (VAC, community, game, trade bans). It does not detail the format or provide examples, but it is sufficient for basic usage. No output schema exists, so description fills the gap reasonably.

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?

Schema coverage is 0%, so description must compensate. It explains that steam_id can be a Steam ID or vanity name and defaults to own profile, adding significant meaning beyond the empty schema description.

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 it retrieves ban status for a Steam player and lists specific ban types (VAC, community, game, trade/economy). It is specific about the verb 'Get' and resource 'ban status', but does not explicitly differentiate from sibling tools like get_player_summary.

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?

Implies usage context by noting the steam_id parameter is optional and defaults to the user's own profile, but no explicit guidance on when to use this tool versus alternatives or when not to use it.

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