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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful magnitude context (9,700+ entries) but says nothing about pagination limits, sharding behavior, or rate considerations beyond what the schema implies. Modest added value on top of the 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?

A single front-loaded sentence with no filler; the entry count and filtering note are both informative. It could be marginally more structured but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the schema fully documents the four optional parameters. The description covers scale and filtering; only the routing relative to sibling store tools is missing, which is a minor gap for a simple read-only listing tool.

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 all four parameters (kind, page, shard, page_size) are already documented with defaults and ranges. The description only alludes to the kind filter and adds no syntax or format detail beyond the schema, so baseline 3 is appropriate.

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 resource ('Jimmy John's store-URL index') with a concrete scope (9,700+ entries), so the agent knows this returns a list of store URLs rather than a single store. It doesn't explicitly contrast with the nearby sibling jimmy_johns_store, so it falls short of full sibling differentiation.

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?

The phrase 'filterable to one page variant per store' hints at the kind filter's purpose, but there is no explicit when-to-use guidance or named alternative (e.g. jimmy_johns_store for a single location, jimmy_johns_nearby for geosearch). The agent must infer the routing.

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