Get player profile

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

Annotations already mark it as readOnly and openWorld (safe, no side effects). The description adds: requires STEAM_API_KEY, works for private profiles (but some fields only for public), and lists which fields depend on profile visibility. No contradiction 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?

The description is a single, well-structured paragraph with no redundant words. Every sentence adds value, including the alternative tool reference and profile visibility details.

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?

Despite having an output schema, the description provides a high-level summary of returned fields and their conditionality (public vs. private). It addresses edge cases and prerequisites, making it sufficient for an agent to understand the tool's capabilities.

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 a description for steamid. The description adds valuable context: 'Omit to use the STEAM_ID configured on the server. Convert a vanity/custom URL name with resolve_vanity_url first.' This goes beyond the schema's raw pattern info.

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 'Get a player's profile by SteamID64' and lists specific fields (display name, online state, etc.). It also distinguishes itself from the sibling tool get_player_bans, which is for ban status.

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 says 'For VAC/game/trade ban status instead, use get_player_bans', providing a clear alternative. It also notes the STEAM_API_KEY requirement and behavior for private vs. public profiles, guiding appropriate use.

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