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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered structurally. The description adds a real behavioral rule not in the annotations ('One licence per person, quantity 1'), which explains why the operation is idempotent and non-destructive, but says nothing about resulting cart state or failure behavior.

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 compact clauses, front-loaded with the Storefront context and the action. No filler, though 'billing variant' is slightly insider vocabulary that could be clearer without costing length.

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 simple two-parameter tool with annotations and no output schema, the description covers purpose and the key business rule. It leaves gaps around the quantity parameter's expected range (schema says integer, description implies always 1) and does not mention auth or cart-state effects.

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 0%, so the description must compensate. It does add meaning: product_id is characterized as a 'billing variant' with an example ('coil-scanner-monthly') and quantity is effectively constrained to 1. It still omits format/type expectations for product_id, so compensation is partial rather than full.

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+resource ('add a billing variant' to the Storefront cart) and gives a concrete example value, so the agent knows exactly what the tool acts on. It does not explicitly contrast itself with remove_from_cart or update_cart_item, but the intent is unambiguous without that.

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?

There is no explicit when-to-use guidance or routing to siblings such as update_cart_item (changing an existing line) or checkout_handoff. The only guidance is a business constraint ('One licence per person, quantity 1'), which is useful but not usage routing.

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