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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine behavioral context: the currency (zloty), the field richness (variants, diameter, stuffed crust), and the market-separation warning. It does not describe pagination or catalog size, but against the annotations it adds solid value.

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 tight sentences, front-loaded with what the tool returns, followed by the one routing caveat. No filler.

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 no explanation, and the description covers the market/currency distinction that matters most here. Slightly short of 5 only because it omits how this Poland tool relates to the general papajohns_menu sibling.

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 single optional 'category' filter is fully described in the schema, so the baseline is 3. The description adds nothing about the filter and does not need to.

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+scope: 'Papa John's Poland priced menu in zloty' with concrete content (variants, pizza diameter, stuffed crust). It explicitly distinguishes itself from the sibling papajohns_russia_menu, so an agent can route without opening schemas.

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 caveat 'Poland shares Russia's platform but is a separate market with its own catalog and currency -- do not compare prices across the two' gives a real usage constraint against a sibling. However, it never states when to prefer this tool over papajohns_menu, papajohns_intl_menu, or other country menus, so guidance is implied rather than explicit.

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