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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description goes further by disclosing the return contents (priced items and deals, dietary tags, images) and the existence of per-store/channel/day availability blackouts, which is useful behavioral context beyond the 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?

Two tight sentences, front-loaded with the core resource and price/return detail, followed by the market-scope caveat. The itemized field list is mildly dense but each element is informative rather than wasted.

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 rich schema, an output schema, and read-only annotations, the description supplies enough context for an agent to call this correctly, including the India-only scope. The only gap is explicit sibling routing (menu_item/deal), which is minor given the structured fields.

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 every parameter (day, tag, store_id, channel_id, category_id, include_options) is already fully documented in the schema. The description only echoes the store/channel/day availability concept without adding syntax or interaction detail beyond what the schema provides.

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 (returns the priced India menu) and enumerates the content (categories, items, deals, list/discount prices, dietary tags, images, availability). It clearly marks itself as India-only and distinct from US data, though it does not explicitly name how it differs in scope from siblings like papajohns_india_menu_item or papajohns_india_deal.

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?

Adds one real usage constraint -- 'India market only, not comparable to Papa John's US data' -- which helps disambiguate from papajohns_menu/intl variants. However, it gives no explicit when-to-use vs alternatives (e.g., use menu_item for a single item, deal for deals), leaving routing to inference.

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