get_friend_list

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

With no annotations, the description carries the full burden. It explains the tool is read-only and returns specific fields, but does not disclose potential error behaviors (e.g., invalid steam_id), rate limits, or authentication requirements. The description is adequate but not 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?

The description is extremely concise, using three short lines to convey purpose, return values, and parameter details. It is front-loaded with the core action and contains no extraneous information.

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 simple tool with a single optional parameter and a known output (friend list), the description provides essential information: what it does, what it returns, and how to use the parameter. The existence of an output schema is mentioned in context, so the description need not detail the output format. It is complete enough for an agent to invoke 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 has 0% description coverage for the parameter. The description compensates by explaining that steam_id is optional, can be a Steam ID or vanity name, and defaults to the user's own profile. This adds meaningful context beyond the schema alone.

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 friends list and details the returned information (friend IDs, relationship status, date befriended). It distinguishes itself from sibling tools which focus on games and achievements.

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?

No guidance is given on when to use this tool versus alternatives. It does not discuss prerequisites, alternative tools for similar tasks, or situations where this tool is inappropriate. The sibling tools are mostly unrelated, but explicit usage context is missing.

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