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 adds that results include slot composition plus every eligible filler item and its price, which is useful structural context beyond the annotations, but it says nothing about pagination, caching, or error behavior for an unknown deal_id.

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?

One dense sentence, front-loaded with the qualifiers (company, country, currency) before the payload list. No filler, though the parenthetical currency note could arguably move into structured data.

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 spelled out, and the annotations carry the safety profile. The remaining gap is operational: with three near-identical Papa John's siblings (india_menu, india_menu_item, intl_deal) the description should have stated which one to call first and why, since an agent cannot infer the deal_id sourcing from the description alone.

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 there is only one parameter, so the schema fully documents deal_id including the provenance rule. The description adds nothing about the parameter, which is acceptable at this coverage level but not additive.

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?

Names the specific resource (Papa John's India deal composition), its scope (Indian Rupees), and the payload shape (slot, quantity, size, eligible items with prices). It is clearly distinct from papajohns_india_menu and papajohns_india_menu_item, though it is phrased as a noun phrase rather than a verb and never states that it takes a deal_id.

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?

There is no when-to-use guidance and no mention of the sibling tools it competes with (papajohns_india_menu, papajohns_india_menu_item, papajohns_intl_deal). The only routing hint lives in the schema description of deal_id, which points at GET /papajohns/india/menu, not in the tool description itself.

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