List web pickup places (AlzaBox, branches, 24/7)

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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds valuable context beyond that: it calls out the live API source, explicitly states no account token is required, and notes the role of `order_id`/`group_id` in checkout context. This is useful supplemental transparency without contradicting annotations.

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 not bloated: it front-loads the core action and API, then adds output forms, use cases, an alternative-tool distinction, context-parameter guidance, and a working example. Every sentence earns its place and the example is compact and illustrative.

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 that an output schema exists and annotations cover safety/idempotency, the description covers the remaining essential context: the upstream API, authentication requirements, intended use cases, related tool dependencies, and context parameters. Nothing critical is missing for correct invocation.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining why `deliveryId`/`parcelShopId` matter to `web_place_order`, describing the `place_id` detail mode, and giving a concrete example that maps `latitude`, `longitude`, `types`, and `limit`. That pushes it above baseline.

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 verb and resource: 'List Alza pickup places from the live m.alza.cz personalPickup/v1 API'. It also clarifies what the tool can return (type-availability counts, paginated list, single-place detail) and explicitly contrasts itself with `delivery_options`, making sibling differentiation clear.

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 concrete use cases: finding pickup places and obtaining `deliveryId`/`parcelShopId` for `web_place_order`. It also gives an exclusion ('Unlike `delivery_options`, this is visitor-readable — no account token required') and advises passing `order_id`/`group_id` from basket checkout context, so an agent knows when and how to use it.

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