steam_get_user_groups

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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds the context of communities/clans, but does not disclose extra behaviors like the cost of enriched lookups or that the steamid is optional for using the configured default user.

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?

Exactly one sentence, front-loaded with the main action and resource. No wasted words or redundancy.

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?

Given the tool has sub-parameters like enrich (which triggers extra lookups), limit, and an optional steamid, a single sentence is too sparse. The rich schema helps, but the description itself is not complete enough to guide an agent on how to invoke correctly or understand trade-offs like the enrich flag.

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 provides no parameter information, and schema description coverage is 0%, meaning the description does not compensate for any parameters. The agent is left to rely entirely on the input schema to understand steamid, enrich, limit, and response_format. No added value 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 'List the Steam groups (communities/clans) a user belongs to' uses a specific verb (List) and resource (Steam groups) with clear scope (a given user). It distinguishes this tool from sibling tools like steam_get_friend_list or steam_get_owned_games.

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 clearly implies the tool is used when you need to see a user's Steam group memberships. However, it does not explicitly mention when to prefer this over alternative sibling tools or exclude any cases, so no explicit when-not guidance is given.

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