Open an Untappd URL (resolve + fetch)

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds useful behavioral context beyond those: it performs two steps (resolve + fetch), does so in one call, and returns a { resolved, detail } shape. This is meaningful for an agent deciding whether this tool satisfies a need.

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 one efficient sentence that front-loads the core action, names its constituent tools, and gives the return shape. Every clause earns its place without redundancy or filler.

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?

This is a simple one-parameter tool with strong annotations and no output schema. The description explains the return value shape and references the matching info tool, which is enough context to call it correctly. It could be more explicit about what 'detail' contains, but that gap is minor for invocation.

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 coverage is 100%, with the single url parameter already described as 'An untappd.com URL to resolve and fetch.' The description adds no new format, normalization, or validation details, so it stays at the baseline 3 rather than earning extra credit.

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 combination—'resolve AND fetch'—and clearly names the resource: an untappd.com URL. It also distinguishes itself by explicitly presenting the tool as a convenience combination of untappd_resolve and the matching info tool, so an agent can separate it from those siblings.

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 usage context: use this when you want both URL resolution and entity detail in a single call. It references the alternative tools (untappd_resolve and the matching info tool), though it doesn't explicitly state when to prefer those separate tools, so it stops short of full exclusions.

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