Get a player's ban status

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

Annotations already declare readOnlyHint and openWorldHint. The description adds valuable behavioral context: it requires STEAM_API_KEY, works even on private profiles, and lists ban types checked. No contradictions with 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?

Highly concise: two sentences with no redundancy. Each sentence adds meaningful information (ban types, use case, public status, API key requirement). Front-loaded with key function.

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 presence of an output schema (handling return values), the description sufficiently covers prerequisites (API key), parameter usage, and behavioral constraints. No obvious gaps for a simple read-only tool.

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 100% with clear pattern and description. The description enhances it by explaining how to obtain the steamid (convert vanity URL with resolve_vanity_url) and that omitting it uses a configured default. This adds clarity beyond the schema.

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 checks VAC, game, community, and economy ban status for a SteamID64, with a specific verb ('check') and resource ('ban status'). It also includes a use-case hint ('useful before trading or adding a friend'), distinguishing it from sibling tools which focus on games, reviews, or player summaries.

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 a clear use case (trading/adding friend) and notes public accessibility. It does not explicitly mention when not to use or name alternatives, but the context is sufficient for appropriate selection.

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