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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the description doesn't need to restate safety. It adds real context beyond that: an authentication requirement and the warning that title and notes are member-authored text, which is a meaningful untrusted-content signal.

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?

Three sentences, front-loaded with the identity and lookup key, followed by return contents and then the auth prerequisite. No sentence is filler, and the member-written-text caveat earns its place.

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 usefully lists the shape of the answer (title, recipient, date, role, items with notes and prices), which is above average for a two-parameter read. Only gap is that market's influence on prices and links is left solely to the schema.

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% with an enum on market, so the structured field already explains both parameters. The description reinforces list_id but says nothing about how market affects the returned links and prices; the schema carries that entirely.

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 ('Returns one list on the signed-in shopper's account by list_id') and enumerates the returned fields, which separates it from list_my_wishlists (enumeration) and get_wishlist (non-account lists). It never names those siblings outright, so differentiation is inferred rather than stated.

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 implied: fetch a single list when you already have a list_id, with 'Requires sign-in' supplying a prerequisite. There is no explicit when-not clause and no pointer to list_my_wishlists for discovering ids or to get_wishlist for lists outside the account.

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