Add OVS product to cart

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, so the agent knows it is a mutative operation. The description adds value by disclosing a preview-confirm-add workflow, which is not evident from the annotations or schema alone. It does not contradict the annotations.

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 description is a single concise sentence that front-loads the action ('Preview, confirm, and add') and includes no unnecessary words. It is efficiently structured and easy to parse.

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?

The tool has 3 parameters, an output schema, and useful annotations, so the description does not need to explain return values or basic safety. The description covers the core purpose and workflow, though the exact role of confirmationToken could be clearer. It is adequate but not exhaustive.

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 0%, so the description must compensate. It references 'OVS product ID' (productId), 'one or more units' (quantity), and 'confirm' (confirmationToken), giving contextual meaning to all three parameters. While not highly detailed, it provides essential semantic cues beyond the raw schema.

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 clearly states the action (add), the resource (OVS product ID), and the scope (to cart), distinguishing it from sibling tools like remove_from_cart. The verb 'add' is specific and directly aligns with the tool's name and title.

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 implies the tool is used to add OVS products to a cart, providing clear context. However, it does not explicitly mention when to use this tool over alternatives or when not to use it, though the sibling context makes this reasonably inferable.

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