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

With no annotations, the description carries the full burden, and it does disclose the key side effect (mutating cart state) and the token return. It says nothing about auth/cart identity, whether re-adding the same SKU increments quantity, idempotency, or failure behavior on an invalid SKU — meaningful gaps for a write operation.

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 sentences with the action and outcome front-loaded and zero filler; nothing could be cut without losing information.

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?

Return values are covered by the output schema, and the add-to-cart-then-checkout flow is conveyed. For a tool with no annotations and 0% parameter coverage, though, quantity semantics and error/auth behavior remain unstated, so it is only minimally adequate.

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 only asserts that a valid SKU is required and gives no format, validity rule, or example; the quantity parameter (default 1) is never mentioned, so its semantics — increment vs. set, valid range — are left entirely undefined.

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 a Salvage & Surplus product to your cart') plus the observable outcome ('receive a cart token'), which cleanly separates it from search_products, get_product, checkout and confirm_payment. An agent can route to it without opening the schema.

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 line 'Returns cart_token needed for checkout' implies this step precedes checkout, which gives implicit ordering guidance. However, no alternative is named, no exclusion conditions are given, and it never says the product must first be located via search_products or get_product.

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