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

Beyond the annotations (readOnlyHint, idempotentHint), the description adds real behavioral context: no resource is created at call time, the returned value is a URL plus per-item matching details, and the list is editable/shareable once opened. This confirms and enriches the readOnly annotation rather than contradicting it.

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 core product is front-loaded in the first sentence, with the no-side-effect caveat and return value following. Slightly dense parenthetical, but every clause carries information and nothing is padded.

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 two-parameter, annotation-backed tool with no output schema, the description covers what the tool produces, its side-effect profile, and its return shape (URL plus match results). Only the sibling-differentiation and item-constraint details are 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 only 50% (city has a description, items does not). The description adds meaning to city ('priced in every branch of the city, when given') and hints at per-item matching, but it says nothing about the items constraints (1–40 items, 2–80 chars each), leaving half the parameter surface to 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 states a specific outcome — a link that turns the given items into a WizStore smart shopping list — with concrete attributes (city pricing, editable, shareable). It is clear what the tool produces, but it never names or contrasts with the very similar sibling price_shopping_list, leaving the agent to guess which one to call.

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?

Usage is only implied: 'Nothing is created until the person opens the link' hints that this is the hand-off-to-human option rather than a direct price computation, but there is no explicit when-to-use statement or reference to alternatives such as price_shopping_list or get_product_prices.

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