Add several products at once

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

Discloses internal behavior: slugs resolved to article IDs, uses bulk endpoint, returns per-item status, and failure condition (404). No annotations provided, so description carries the burden well.

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 concise sentences: first states purpose, second adds critical context. No redundancy.

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?

Given one parameter and no output schema, the description covers prerequisites, behavior, and error condition completely. No gaps.

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 covers 100% of parameters but description adds meaning: 'Each item is a product slug + quantity' clarifies the structure beyond the schema's minimal 'Products to add' description.

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 tool's purpose: 'Build a basket in one call' with multiple items specified by product slug and quantity. This is specific, distinct from the sibling add_to_cart which likely adds a single product.

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?

Explicitly states prerequisites: 'Requires sign-in AND an existing cart: call set_delivery_slot first, otherwise this fails with 404.' Provides clear guidance on when to use it and what not to do.

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