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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the description's job is to add context — and it does, describing exactly what each record contains: per-channel hours, payment methods, delivery zones with minimum-order thresholds, and live open flags. It does not discuss pagination behavior beyond the schema, keeping it out of 5 territory.

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?

Two sentences, front-loaded with the market scope, no filler. The dense field enumeration is information-carrying rather than padding, though it is a long clause to parse.

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 a 7-parameter schema, annotations, and an output schema present, the description need only orient the agent — which it does by naming markets, the fields returned, and the downstream dependency on the priced menu. Nothing critical for correct invocation is missing.

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% with 7 well-documented parameters (market enum inline, store_id vs latitude/longitude modes, page/limit, fulfillment). The description adds no parameter syntax or format detail beyond what the schema already states, so the baseline 3 applies.

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 (Papa John's restaurants) and enumerates the exact markets covered, plus the fields returned, so an agent can tell it apart from papajohns_store or papajohns_nearby. It stops short of naming a sibling to defer to, which is what separates a 4 from a 5.

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 final clause ('Returns the store id the international priced menu needs') implies the use case, chaining this tool into papajohns_intl_menu. But there is no explicit when-to-use vs when-not, and no mention of papajohns_store, papajohns_nearby, or papajohns_india_stores as alternatives.

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