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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds real behavioral context: definitions of shelf_total, effective_total and club_total, the ranking rule (chains selling every item first, by shelf_total), and the caveat that effective/club are best-case across branches rather than one real branch.

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?

Dense but front-loaded: the core purpose and the city exclusion come first, then total definitions, then the sibling pointer. It is longer than minimal, but nearly every clause carries distinct semantic value; the parenthetical 'a typical branch' aside is the only trim candidate.

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 must describe return semantics, and it does: per-chain totals, item counts, missing items, and ranking order. An agent has enough to interpret and use the result without guessing.

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% and the schema already documents the single 'items' parameter with format, limits and an example. The description adds no parameter-level detail, so baseline 3 is appropriate — it neither compensates nor detracts.

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 (compare) and resource (shopping list across retail chains) and immediately scopes it with 'no city needed'. It clearly distinguishes itself from price_shopping_list, which is the sibling that handles city-level branches.

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 tells the agent when this is the right tool (chain-level comparison, no city) and names the alternative for the other case: 'for real branches in one city use price_shopping_list'. The routing condition is unambiguous.

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