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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description contributes the shape of the payload (family, default vs premium classification, per-size cost), which is useful context, but adds nothing on auth, market scope, or rate behavior. Adequate against the lower bar set by 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 dense sentence front-loads the resource and then lists the returned attributes. No padding or repetition, though the long enumerated clause is slightly heavy for one sentence.

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 an output schema present, the description need not detail return structure, and all three parameters are schema-documented. It supplies the semantic content of the catalog, which is the main missing piece. The only gap is sibling routing, which is minor for a simple read-only catalog.

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 market, menu_id, and category are already fully documented, including the category enum values. The description's phrase 'for one international menu' and 'at each size' loosely maps to those parameters but adds no syntax or format detail beyond the schema. 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: the ingredient catalog for one international menu, enumerating the exact contents (toppings, sauces, cheeses, family, default/premium rate, per-size extra cost). It is clearly distinguishable from siblings like papajohns_intl_menu or papajohns_intl_product, though it never names them explicitly.

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?

No guidance on when to pick this over papajohns_intl_menu, papajohns_intl_product, or the market-specific menus. The description only describes what is returned, never the conditions or alternatives that would select it.

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