add_to_wishlist

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

No annotations are provided, so the description carries the full behavioral burden. It discloses the basic add action and prerequisite workflow, but it does not mention authentication requirements, duplicate behavior, whether the tool can auto-create a wishlist, or what happens if wishlistId is omitted. The internal contradiction between the description and the schema's name parameter further reduces transparency.

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?

Two sentences, no wasted words. The core action is front-loaded, and the prerequisite guidance follows naturally. It is concise without being under-specified in structure.

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 write operation with no annotations and no output schema, the agent needs more information about auth, how to choose between wishlistId and name, and duplicate handling. The description mentions key prerequisite tools but leaves the auto-create ambiguity unresolved, so it is not complete enough for confident invocation.

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%, so the baseline is 3. The description adds useful practical context for productId by pointing to search_products, but it does not clarify the relationship between wishlistId and name, leaving the schema to carry most parameter meaning.

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 a product to a Webhallen wishlist. It is clearly distinguished from sibling tools like create_wishlist, delete_wishlist, and list_wishlists because the action is item-level addition rather than list management.

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 description explicitly names two sibling tools and their preconditions: use search_products to get the product ID and use create_wishlist if the list does not exist. However, the input schema's name parameter says 'If wishlist doesn't exist, create one with this name,' which slightly conflicts with the instruction to use create_wishlist first, muddying when this tool should create versus only add.

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