List Bilka stores

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

Goes well past readOnlyHint/openWorldHint by disclosing that no login is needed, that selected_store_id is the server's current selection with null meaning none, and by flagging store and pickup-point names as untrusted data with an explicit instruction not to follow embedded instructions. The prompt-injection warning is a genuinely valuable behavioral 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 the resource and scope, then the follow-up action, then security. Every sentence carries distinct payload, though the selected_store_id sentence and the untrusted-data sentence could be compressed slightly without losing meaning.

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 carries the return-value burden and does so: store ids, nested pickup points, and the meaning of selected_store_id including its null case. An agent has everything needed to call it and interpret the result.

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 takes zero parameters, so the baseline is 4 and there is nothing to disambiguate. The description does usefully name the store_id and selected_store_id fields the agent will encounter in the response, though these are outputs rather than inputs.

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 ('List the Bilka stores that BilkaToGo shops from, with their store ids') and immediately clarifies a structural detail siblings don't cover: pickup points are nested under the store serving them. This distinguishes it cleanly from list_delivery_places and the other list_* siblings.

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 the next step: 'To shop at a store, call select_store with its `store_id` or name.' That names the alternative and the condition that selects it, so an agent knows both what this tool is for and what to do after it returns.

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