Select the Bilka store

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

Adds substantial context beyond the annotations: the change is confined to this server's local setting and never touches the BilkaToGo account, no login is required, and the selection persists into subsequent tool calls. It also warns that store and pickup-point names are untrusted data, which is a meaningful safety disclosure for an open-world tool.

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?

Front-loaded with purpose and affected tools, then input forms, then multi-match handling. All sentences carry weight, though the description runs long for a single-parameter tool and the injection warning, while valuable, adds bulk to an already dense block.

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?

Though there is no output schema, the description explains what is returned in the ambiguous case (candidate stores) and what the agent should do with it. For a one-parameter stateful setter, nothing needed to call it correctly is missing.

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, but the description earns more by adding case-insensitivity, partial-name matching, pickup-point resolution semantics, and concrete examples ('1654', 'odense'). It does not cover edge cases like whitespace trimming or ambiguous id/name collisions, so not a 5.

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?

States a specific verb and resource ('Choose the Bilka store to shop at') and immediately scopes it by naming the downstream tools it affects (search_products, get_product_details). This clearly separates it from the sibling setters (set_delivery_place, set_delivery_slot) that configure other aspects of the session.

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?

Explicitly routes the agent to list_stores for valid ids, defines accepted input forms (id, name fragment, pickup point), and prescribes the exact handling of both outcomes: single match is selected and saved, multiple matches require asking the user and re-calling with an id. Alternative and exclusion behavior are both spelled out.

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