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 goes beyond annotations by disclosing the returned attribute set and the ordering constraint (hours are split per order channel), which is genuine behavioral context. It stops short of describing pagination or result limits.

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, zero filler, with the returned-field inventory front-loaded and the downstream linkage placed last where it belongs. Every clause carries information.

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 not be explained, and the description still notes the per-channel hours shape. The linkage between store ids and the menu availability filter is the key operational fact an agent needs. Minor gap: no indication of result size or pagination for a full-country store list.

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 channel_id param is fully documented with its four values in the schema itself. The description restates the same channel list without adding format or syntax beyond what the schema provides, so 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 INDIA restaurant list) and enumerates what each record contains: address, phone, coordinates, weekly opening hours per order channel. It implicitly distinguishes itself from the broader papajohns_intl_stores and country-agnostic papajohns_directory by scoping to India, though it never names the sibling it is not.

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 final sentence ('These store ids key the India menu's availability filter') hints at intended downstream use, which is implicit usage guidance. However, there is no explicit when-to-use, no when-not-to-use, and no named alternative among the many store/menu siblings, leaving the routing decision to inference.

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