Get player profile

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

Beyond the readOnlyHint and openWorldHint annotations, the description discloses the STEAM_API_KEY requirement and the private-profile behavior where country, account age, and current game only populate for public profiles. This is valuable contextual information that enriches the agent's understanding of side effects and response variability.

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, front-loaded with the main purpose, and every sentence adds substantive value—purpose, auth requirements, privacy caveats, and alternative tool. No filler or repetition.

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 read-only profile lookup tool with an output schema present, the description sufficiently covers the essential nuances (auth, private profiles) and the distinction from a sibling tool. The output schema handles return value details, so no further information is needed.

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 input schema already provides a full description of the steamid parameter, including format, default behavior when omitted, and conversion guidance via resolve_vanity_url. The description does not add further meaning beyond referencing the ID type, so the baseline score of 3 for high schema coverage 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 identifies what the tool does: retrieves a player's profile using SteamID64 and enumerates the specific fields returned (display name, online state, country, account age, Steam level, current game). This explicit verb-resource structure distinguishes it from siblings like get_player_bans, which handles a different purpose.

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 explicitly states when not to use this tool: 'For VAC/game/trade ban status instead, use get_player_bans.' This provides a clear exclusion and names an alternative, meeting the highest bar for usage guidance.

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