web_get_favorites

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

No annotations are provided, so the description carries the transparency burden. It signals a read-only retrieval operation via 'abrufen' and scopes it to the customer account, but it does not disclose authentication requirements, behavior for an empty or missing favorites list, or explicitly confirm there are no side effects. For a simple getter with an output schema, this is adequate but not detailed.

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 description is a single, compact German sentence with no filler. The key object and scope are front-loaded, making it easy for an agent to parse quickly.

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 zero parameters, the presence of an output schema, and the clear one-sentence purpose, the description is largely complete. It could add a note on when to choose this over web_get_cart_list or web_get_order_list, but that is not essential for a no-argument favorites retrieval tool.

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 tool has zero parameters, so the empty schema is fully self-explanatory and description coverage is vacuously 100%. No parameter-level documentation is necessary, and the description correctly adds no misleading parameter detail.

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 the specific verb 'abrufen' and identifies a clear resource, 'die im Webshop-Kundenkonto gespeicherte Favoritenliste' (the favorites list stored in the webshop customer account). This distinguishes it from siblings such as web_get_cart_list, web_get_order_list, and web_search_articles.

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?

Usage context is implied: call this when the agent needs the customer's saved favorites list. The description does not explicitly contrast it with alternatives or state when not to use it, but the scoping to 'Webshop-Kundenkonto' gives reasonable contextual guidance for a simple no-parameter getter.

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