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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this is a mutating external operation. The description adds the editToken requirement, but does not explain mutation effects, duplicate handling, or required permissions beyond that token. With annotations covering the safety profile, this is adequate but limited.

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 purpose is front-loaded in a short two-sentence description with no redundant explanation. The trailing 'OpenAPI: addWishlistItem' is a minor operational reference that adds little for an agent, but overall it is appropriately concise.

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 mutation tool with nine parameters, low schema description coverage, no output schema, and several undocumented item fields. The description does not explain whether at least one identifying field such as url, asin, name, or catalogId is required, nor what happens after the item is added. For a tool of this complexity, the description is too thin.

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 22%, and eight of the nine parameters are undocumented. The description mentions editToken, which the schema already describes, and adds no guidance on how url, asin, name, title, catalogId, emoji, or searchKeywords should be used or combined. The description does not compensate for the low schema coverage.

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 verb and resource: 'Add an item to a wishlist.' This clearly distinguishes it from create_wishlist and get_wishlist. It does not explicitly contrast with create_and_fill or other sibling tools, 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?

The prerequisite 'Requires editToken from create' gives useful context for invocation. However, the description does not say when to use this tool versus create_and_fill, create_wishlist, or resolve_product, leaving alternatives unaddressed.

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