steam_get_user_groups

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

With readOnlyHint=true already present, the description's 'List' is consistent and adds no contradiction. It adds modest domain context by clarifying that groups are communities/clans, but it doesn't disclose defaults, enrichment cost, or output shape—those live in the schema.

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?

A single front-loaded sentence with no filler. The parenthetical 'communities/clans' earns its place by disambiguating domain terminology.

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 listing tool with a well-documented schema and annotations, the description is nearly complete for selection and invocation. It doesn't hint at the optional steamid default or the extra-lookup cost of enrichment, but those are covered in the schema, and no output schema is needed for a simple listing response.

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 description mentions no parameters, but the input schema documents each one clearly (limit, enrich, steamid, response_format) with defaults and examples. Since the schema carries the parameter semantics, the description's silence is an acceptable baseline rather than a gap.

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 names a specific verb (List), resource (Steam groups/communities/clans), and scope (a user belongs to), making the tool's function unambiguous. No sibling tool targets user groups, so the purpose is clearly distinct within the toolset.

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 implicitly states when to use it: whenever a user's Steam groups are needed. There are no overlapping sibling tools, so explicit exclusions are unnecessary; however, the description gives no guidance about when to disable enrichment or how to handle an omitted steamid.

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