Get Untappd user wishlist

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the description's 'Read-only' adds no new information. It does add the useful behavioral note about sorting and paging, and hints at identity handling by saying 'Omit username for your own account,' but it does not discuss rate limits, response shape beyond the schema, or other side-effect-related 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 short and front-loaded with the core purpose. The only minor redundancy is the final 'Read-only' sentence, which repeats information already present in the annotations. Otherwise, every sentence is concise and contributes a distinct idea.

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, paged list tool with no required parameters and full schema coverage, the description provides sufficient operational context: what it returns, that it supports sorting and paging, and how to target the caller's own account. The lack of an output schema is partially mitigated by the 'view' parameter's detailed explanation of both compact and full response shapes. The main gap is the absence of guidance on when to prefer this tool over a sibling like untappd_user_beers.

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%, so all five parameters are already documented in the input schema. The description only restates that sorting and paging are supported and that the username is optional, adding little beyond the structured parameter descriptions.

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 ('Get') and a specific resource ('beers on a user's wishlist'). This clearly identifies the tool's function and distinguishes it from the many sibling tools such as untappd_user_beers or the wishlist add/remove operations.

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 no guidance about when to use this tool versus alternatives. It mentions that the username can be omitted for one's own account, but does not explain how this tool relates to sibling user tools like untappd_user_beers or when one would choose the wishlist over other beer-listing endpoints.

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