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

With readOnlyHint and openWorldHint already declared, the description adds real context: prices are in US dollars and the result is a size-and-crust price matrix rather than flat items. It doesn't cover pagination or freshness of pricing, but for a read-only catalog tool this is solid disclosure.

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 resource and the differentiating fact (own platform). No filler, no restatement of the tool name.

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?

The tool is simple (one optional param, output schema exists, annotations present), and the description supplies currency and result shape, so an agent has enough to call it correctly. Minor gap: no guidance on how it relates to the other country menus beyond the international one.

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% and the single optional 'category' parameter is documented in-schema with example values (Pizzas, Entradas, Postres, Extras). The description never mentions filtering, so it adds no meaning beyond the schema — 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 verb+resource (Papa John's El Salvador priced menu) and even characterizes the payload: each product with its full size and crust price matrix. It also explicitly distinguishes itself from the international menu tool, so an agent can route without opening the schema.

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 description gives a clear routing rule by naming the alternative ('separate from the international menu tool'), implying this tool is for El Salvador queries specifically. It does not, however, address the other country-specific siblings (Colombia, Peru, Poland, Russia, India), which an agent might confuse when the country is not stated.

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