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

Annotations already declare this is a write (readOnlyHint=false) with open-world reach. The description adds real behavioral context beyond that — edit token provenance and the warning that token storage may mint a new id so bookmarks must be updated. It still omits duplicate-handling, failure modes, and any indication of return shape beyond the passing "prefer buyUrl in responses" note.

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?

Extremely dense and front-loaded — the action comes first, then prerequisites, then accepted body fields, then the token-storage caveat. The telegraphic phrasing ("Body: name/title plus…") is terse but readable; the OpenAPI name at the end is marginally expendable.

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 9-parameter mutation with no output schema, the description covers prerequisites, most accepted item fields, and the token-rotation caveat. It still leaves emoji and id undocumented and says nothing about behavior on invalid identifiers or duplicate items, leaving visible 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 22%, so the description has to carry weight and largely does: it names name/title, asin, url (with the "pasted /dp" format hint), searchKeywords, catalogId, and editToken's required provenance. Only emoji and the id parameter go unmentioned, so this meaningfully compensates for the coverage gap.

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 first sentence gives a specific verb and resource ("Add an item to a wishlist") and the trailing OpenAPI operation name pins it to addWishlistItem. It doesn't explicitly distinguish itself from siblings like create_and_fill, which also appear to populate wishlists, so it falls short of a 5.

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?

"Requires editToken from create" is a useful prerequisite and implies this follows a create/mutate step, so usage is implied. But it never states when to pick this over create_and_fill or create_wishlist, and there are no exclusions or alternatives named.

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