Get a player's friend list

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

Discloses that list is capped at 100 most-recently-added, provides check via 'returned' vs 'total', and explains failure case (found:false if not public). Annotations (readOnlyHint, openWorldHint) are complemented.

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?

Single paragraph, front-loaded with core functionality, followed by caveats and alternative. Every sentence adds value; no 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?

Covers all needed context: output fields, pagination hint, error conditions, and prerequisite steps. Output schema exists, so return details are optional but description adds extra clarity.

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?

Description adds meaning beyond schema: explains that omitting steamid uses server-configured ID, and advises converting vanity URLs via resolve_vanity_url. Schema coverage is 100%.

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 verb 'List', the resource 'a player's Steam friends', and includes specific fields (name, online state, current game, friendship duration). It also distinguishes from sibling tool find_friends_who_own.

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?

Explicitly says when to use the alternative tool (find_friends_who_own), mentions prerequisites (STEAM_API_KEY, public friends list), and instructs to convert vanity URLs using resolve_vanity_url.

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