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

Annotations only declare readOnlyHint=false and openWorldHint=true, so the description usefully adds that an editToken is required and that token storage may return a new id, prompting bookmark updates — a real side effect an agent would otherwise miss. It does not cover duplicate handling, validation failures, or partial-success behavior, keeping it below a 5.

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?

Front-loaded with the action, followed by prerequisite, body options, and the token caveat — all dense and free of filler. The trailing "OpenAPI: addWishlistItem" is marginal value for an agent but is one short clause, not padding.

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 10-parameter mutation tool with no output schema, the essentials are present: the required list id and editToken, the identifier alternatives for the body, and the token-rotation side effect. Remaining gaps (emoji, packed, returned payload shape) are minor and mostly self-describing from 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 coverage is only 20%, so the description has to carry the load, and it does the most important part: it explains that a name/title is supplied alongside one of asin, url, searchKeywords, or catalogId, conveying an implicit one-of choice among identifiers. It also adds the non-obvious format hint for url ("pasted /dp"). It leaves emoji, packed, and the id/editToken fields to the schema, so it is not exhaustive.

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?

States a specific verb and resource ("Add an item to a packing list") plus the underlying API operation (addWishlistItem), so the agent knows exactly what is created. It is distinguishable from create_packing_list and search_packing_items by implication, but never names a sibling or explicitly contrasts itself.

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" gives the one real prerequisite and implies the call belongs after create_packing_list, which is useful sequencing guidance. However there is no explicit when-to-use/when-not framing or naming of alternatives such as search_packing_items for checking whether the item already exists.

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