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

With no annotations, the description carries the full behavioral burden yet says nothing about what happens on duplicate items (merge vs new line), whether a cart/address must pre-exist, auth/login requirements, or failure behavior. The presence of a notification_message param hints at a follow-up-message workflow that is never explained.

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 short, front-loaded sentences with no filler; the required-inputs note and the item-type constraint are efficiently placed. Minor redundancy with the schema's own 'default menu' note keeps it from a 5.

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 an 11-parameter mutation tool with no annotations and no output schema, the description is thin: it omits cart-state return behavior and the multi-step flow implied by the step-numbered fields and notification_message. The complete schema covers parameters, but behavioral context an agent needs is sparse.

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 schema already explains each field including id sources and the 'menu' enum. The description's notes on vendor id, item id, and item type largely restate schema content, so baseline 3 applies with little added 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?

States a specific verb and resource ('Add an item to cart'), making it clearly a cart-mutation tool distinguishable from siblings like view_cart, clear_vendor_cart, and remove_cart_item. It does not explicitly contrast with duplicate_cart_pack, but the core action is unambiguous.

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?

Points to the required discovery path (search_product products[] or view_vendor_items) to obtain vendor and item ids, which implies you must search before adding. However it never states when to prefer this over siblings like duplicate_cart_pack, nor any exclusion such as checking view_cart first.

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