Get your Untappd notifications

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

The description states 'Read-only,' which matches the readOnlyHint annotation but adds no new behavioral information beyond it. It does provide useful context about the account scope and included item types, but does not disclose details such as ordering, pagination behavior beyond schema parameters, or whether the operation requires authentication.

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 a single sentence that front-loads the verb and resource, then adds a compact list of notification categories and scope. It is concise, direct, and contains no filler or repetition beyond the useful 'Read-only' note.

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 simple, read-only, two-optional-parameter list operation, the description is complete: it states the resource, scope, and content types, and the schema already documents pagination. No output schema exists, but the description's category list sufficiently conveys what the response will contain.

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?

Input schema coverage is 100%, with both limit and offset fully described including defaults, minimums, and maximums. The description adds no parameter-specific meaning, so the schema carries the weight; baseline 3 is appropriate.

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 ('Get') and resource ('your Untappd notifications'), scopes it to YOUR account, and enumerates the notification categories (toasts, comments, friend requests, badges, news items). This clearly distinguishes it from sibling user-lookup tools like untappd_user_badges or untappd_activity_feed by emphasizing the current user's notification feed rather than a generic or other-user resource.

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 gives clear context: it is for the authenticated user's own notifications, including specific types. It does not explicitly name alternatives or say when not to use it, but the 'YOUR account' scoping and category list are enough to imply the appropriate use case and separate it from user-specific and activity-feed siblings.

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