List BilkaToGo delivery and pickup places

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

Beyond the readOnlyHint and openWorldHint annotations, the description adds meaningful operational context: it needs a BilkaToGo login, reading changes nothing, home delivery uses place id "home", the address is never shown, and store/pickup names are untrusted data that must not be followed as instructions.

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 dense but front-loaded and every sentence adds value: it covers purpose, return fields, workflow, authentication, read-only behavior, and a prompt-injection warning. There is no 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?

With no output schema, the description appropriately explains the relevant returned fields and current_place_id. It also covers authentication, safety, and follow-up tool calls, making the definition complete for an agent to invoke and use this tool 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?

The tool has zero parameters, so the baseline is 4. The description still adds useful meaning about the returned data, including place_id, kind, store_id, minimum_order, and current_place_id, but parameter semantics are not applicable here.

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 states a specific verb and resource: list where the user's BilkaToGo cart can go, including home delivery, store pickup, and standalone pickup points. It clearly distinguishes the tool from siblings like set_delivery_place and list_delivery_slots by explaining that this is the comparison/discovery step.

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 gives explicit workflow guidance: compare places, suggest one to the user, and once they agree call set_delivery_place and then list_delivery_slots. It also explains relevant conditions, such as delivery slots differing per place and home delivery possibly being sold out when pickup is not.

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