Get Untappd user profile

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, so the 'Read-only' mention is redundant. The description adds the behavioral nuance of omitting username for the configured account and enumerates return content, but it doesn't disclose error handling or rate-limit behavior.

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 three short sentences with the main verb and resource front-loaded. Each sentence earns its place: purpose, usage hint, safety note. No filler or redundancy beyond the minor 'Read-only' repetition.

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?

With no output schema, the description names the expected return fields, giving an agent a clear idea of the response. The two optional parameters are fully explained in the schema, and the sibling list provides enough context for routing. Only explicit alternative-tool routing is missing.

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?

Schema description coverage is 100%, and both 'view' and 'username' already carry detailed descriptions in the schema. The tool description's 'Omit username for your own account' repeats the schema text, so it adds no new semantic value beyond the baseline 3.

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 uses a specific verb and resource ('Get an Untappd user's profile') and enumerates the exact contents (bio, location, total check-ins, distinct beers, badges, stats). This clearly distinguishes it from sibling user_* tools that return detailed check-in or badge lists.

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 provides clear context about what this tool returns (a profile summary) and gives the key usage instruction to omit username for your own account. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of a 5.

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