get_player_summary

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

No annotations are provided, so the description must carry all behavioral disclosure. It describes the return fields and default parameter behavior, but does not explicitly state that the operation is read-only, nor mention potential errors or rate limits. For a simple lookup tool, this is adequate but not comprehensive.

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 very concise, front-loading the main purpose in a single sentence, then listing return values and parameter info. Every sentence adds value with no redundancy or fluff.

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?

The tool is simple (one optional parameter, no output schema), and the description adequately explains purpose, return values, and parameter semantics. It could mention error handling or the exact format of the steam_id, but overall it provides sufficient context for an agent to use the tool correctly.

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 only provides type and default, but the description adds crucial context: steam_id can be a Steam ID or a vanity name, and defaults to the user's own profile. This significantly clarifies parameter usage 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 fetches a Steam profile summary and lists specific return fields (display name, online status, profile URL, currently playing game). This distinguishes it from sibling tools like get_player_stats or get_friend_list, which serve different purposes.

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 mentions the optional steam_id parameter and its default behavior, but does not explicitly guide when to use this tool versus alternatives. Implicitly, it is for basic profile info, but no when-not or direct sibling comparisons are provided.

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