web_get_cart_list

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

With no annotations, the description carries the full burden. It communicates that this is a read/list operation returning all carts including the active one, which is useful. However, it does not disclose whether authentication/session context is required, how cart ordering works, or whether any implicit filtering applies beyond 'customer.'

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 entire description is one compact, front-loaded sentence: the action and resource come first, followed by output details and the active-cart distinction. There is no filler or redundant explanation.

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 zero-parameter read/list tool with an output schema, the description covers what the tool returns and its key distinguishing scope: all customer carts including the active one. It could add an explicit contrast with web_get_cart, but nothing essential is missing for an agent to invoke it correctly.

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?

There are zero parameters and schema coverage is 100%, so there is nothing for the description to clarify about parameters. The baseline for a zero-parameter tool applies, and omitting parameter details is appropriate.

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 names a specific action ('auflisten') and resource ('alle Warenkörbe des Kunden'), plus the return fields (ID + Name) and the active-cart inclusion. The plural 'Warenkörbe' clearly separates it from the sibling web_get_cart without needing to open schemas.

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 for enumerating all customer carts and explicitly notes the active cart is included. However, it never says when to prefer this over the sibling web_get_cart or web_get_order_list, and offers no exclusions, so the agent must infer the use case from the name.

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