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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only safety profile is covered. The description adds one genuinely non-obvious trait: entries vary in shape ('coordinates or structured address depending on which page section the entry came from'), which hints at heterogeneous records. It stops there, saying nothing about pagination limits or total-count behavior.

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 densely-packed sentence with no filler, and the paginated-scope fact is front-loaded ('One page of...'). The parenthetical field list is slightly awkward but earns its place by flagging the shape variance.

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 the description is not obliged to enumerate return values, and pagination is fully covered by the schema. What is missing is the routing context: with a sibling like shakeshack_nearby performing a similar store-listing job, the definition never states which to pick, leaving a real selection gap for a simple read 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%: page and page_size both carry their own default and range documentation. The description adds no parameter-level detail beyond what the schema states, which is the expected baseline when the schema does the heavy lifting.

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 names the specific resource ('Shake Shack's store index') and makes the paginated nature explicit ('One page of...'), so an agent can tell it apart from the single-store sibling. It does not, however, explicitly contrast itself with shakeshack_nearby, which also enumerates stores, leaving a small ambiguity.

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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives such as shakeshack_nearby or shakeshack_store. The agent must infer from the name alone that this is the bulk index rather than a proximity or single-store lookup.

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