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

With no annotations, the description carries the disclosure burden, and it does so well by explaining that the tool returns self-reported facts, including what the store has NOT stated. It also prescribes the agent's behavior around unknown/not_stated gaps. It does not explicitly state read-only status or mention authorization, but the 'store says about itself' framing and get_ name imply a safe, non-mutating operation.

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 longer than average but each clause earns its place: scope boundary, content inventory, example queries, and the critical unknown/not_stated policy. It front-loads the core 'not about one item' distinction. It could be tightened slightly, but there is no padding.

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 compensates by detailing what the agent will find: business identity, location, capacity, policies, hours, ordering contact, product counts, price range, and notably what is not stated. Combined with 100% parameter schema coverage and explicit usage rules, the agent has enough to call the tool and interpret results 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?

Schema description coverage is 100%, so the baseline is 3 even without parameter detail in the description. The sole parameter 'store' is already documented in the schema, including the omit behavior for multi-store endpoints. Nothing further is needed.

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 identifies a specific operation: retrieving a business's self-declared information, not item-level data. It explicitly distinguishes itself from item-focused siblings via 'not about one item' and enumerates the information categories an agent can expect. The 'get' + resource framing makes selection obvious.

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 when-to-use guidance: call it for 'how many do you have', 'how do I order', and 'what is your phone number', and before answering suitability questions. It also states a clear when-not-to-act rule: never fill gaps the 'unknown' or 'not_stated' lists name, and instead tell the shopper to ask the business. This is strong routing guidance relative to siblings.

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