web_get_cart

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

There are no annotations, so the description carries the burden. 'Abrufen' indicates a read-only retrieval, and 'keine Preise' discloses a key output limitation. It does not discuss auth or side effects, but for a simple GET-like cart read this is reasonably transparent.

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?

One compact sentence with no filler. It front-loads the action and resource, and the parenthetical adds essential constraints efficiently.

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 one-parameter read tool with an output schema, the description covers what is retrieved, the quantity semantics, and the no-prices limitation, while the schema covers the active-cart behavior. Nothing essential is missing.

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?

The single optional cart_id parameter is already fully described in the schema, including the null/default behavior. The description adds no parameter-level meaning beyond what the schema provides, so the high-coverage baseline of 3 applies.

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 uses a specific verb ('abrufen') and a clear resource ('Inhalt eines Warenkorbs'), then narrows the scope with 'Positionen mit Menge, keine Preise'. This differentiates it from sibling tools like web_get_cart_list and price-related tools.

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?

It provides clear context: use this tool to retrieve cart contents with quantities, not prices. The schema adds that omitting cart_id targets the currently active cart. It does not explicitly name sibling alternatives, but the 'keine Preise' note signals a relevant exclusion.

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