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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description adds genuinely new behavior: the editToken requirement, the caveat that token storage may return a new id so bookmarks must be updated, and a preference for buyUrl in responses. That is meaningful context beyond the annotations, though nothing is said about error handling or duplicate items.

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?

Dense and front-loaded: purpose first, then token requirement, then body inputs and caveats. The telegraphic style and the trailing 'OpenAPI: addWishlistItem' reference are low-value filler, but nothing is bloated.

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 mutation tool with no output schema, it covers the token lifecycle and item identity but omits the response shape beyond a buyUrl hint, the marketplace parameter's practical necessity, and behavior on invalid/incomplete identity inputs. Adequate but with clear gaps.

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 only 36% across 11 params, so the description must compensate; it does add useful semantics ('url (pasted /dp)' and the either/or item-identity options) but leaves emoji, locale, and the critical marketplace requirement unaddressed. Partial compensation warrants a 3.

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?

Opens with a specific verb+resource: 'Add an item to a gift list / wishlist', and parenthetically scopes it as shopping-list building. It names the prerequisite token (from create) but does not explicitly contrast with siblings like create_and_fill or create_wishlist, so sibling differentiation is only implied.

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?

It states the prerequisite ('Requires editToken from create') and lists the alternative item-identity inputs (asin, url, searchKeywords, catalogId), which implies when this call applies. But it never says 'use create_and_fill instead when…' or covers failure/duplicate cases, so guidance remains implied rather than explicit.

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