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

Annotations declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuinely useful behavior beyond them, notably that prices vary by restaurant and that include_options inflates the response size, which guides the agent on cost of calling.

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 with the scope and contents front-loaded, then the parameter guidance. No filler, though the store_id/include_options notes are near-duplicates of schema text.

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 and read-only annotations present, the description supplies adequate coverage: what the menu includes, how prices are scoped, and the cost tradeoff of options. Missing only explicit sibling routing, a minor gap.

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 parameter descriptions already explain store_id sourcing and include_options default/large-size behavior. The description's mentions of store_id and include_options largely restate the schema, adding only marginal framing.

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 and resource ('Papa John's US/Canada STORE-PRICED menu') plus scope and contents: every category, section and product with price, calories and serving size. The US/Canada and store-priced qualifiers clearly separate it from papajohns_intl_menu and papajohns_menu_item.

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?

Gives concrete usage direction: pass a store_id from the locator tools, and set include_options for sizes/crusts/prep choices. It does not explicitly route the agent to siblings like papajohns_menu_item or papajohns_nutrition, so it stops short of full when-to-use vs alternatives guidance.

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