Change the BilkaToGo delivery place

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

Beyond annotations, the description explains concrete consequences: changed fees, changed minimum order, and potentially a different store whose prices and stock apply. It also discloses persistent side effects on the saved search store, slot compatibility issues, return contents, and a prompt-injection warning about untrusted Bilka text.

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 primary action is front-loaded, and the remaining sentences carry distinct operational details: side effects, slot handling, return value, authentication, payment boundary, and untrusted-data warning. Despite its length, there is little repetition or filler.

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 destructive, open-world mutation with no output schema, the description is complete: it covers prerequisites, side effects, return values, cross-tool follow-up, and security concerns. An agent has enough information to decide whether and how to call it safely.

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 schema already fully documents the single place_id parameter, including its pattern and examples, so the baseline is high. The description adds useful meaning by tying place_id to list_delivery_places and explaining that the selected place changes delivery/pickup mode and potentially the underlying store.

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, 'Switch,' and a precise resource, the user's BilkaToGo cart delivery or pickup place, with a clear pointer to list_delivery_places. It also distinguishes the tool's effect from select_store while noting the overlapping store-selection behavior.

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 states exactly when to use the tool ('Only switch when the user asked for it or agreed to it') and how to recover if the new place does not support the existing slot by calling list_delivery_slots and set_delivery_slot. It also names prerequisites such as a BilkaToGo login and clarifies that ordering and payment remain on the website.

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