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 genuinely useful context beyond that: the currency (Indian Rupees) and the shape of the return (a full customization tree with per-size, per-option pricing), which tells the agent this is a deep detail call rather than a flat lookup.

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 that front-loads the brand, region, and currency before enumerating the customization layers. No filler, no repetition of the title, and every clause conveys scoping or content 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?

For a one-parameter read tool with an output schema, this is close to complete: region, currency, and return shape are all disclosed, and return-value structure need not be restated given the output schema. The only gap is the missing pointer to which listing tool produces the item_id.

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%, so the sole parameter (item_id, plus its origin as a saleitem_id) is already fully documented in the schema. The description adds no syntax, format, or constraint detail beyond that, so the baseline 3 for schema-complete tools 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 item detail, and enumerates what the record contains (sizes, crusts, toppings, dipping sauces, drizzles, base sauces with prices). The India scope and INR currency distinguish it from the intl/generic siblings, but it never names the closest sibling (papajohns_india_menu) as the listing counterpart, so differentiation is implied rather than stated.

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?

Usage is only implied — 'one item's detail' signals a per-item lookup, but there is no explicit when-to-use, no exclusion, and no named alternative. The prerequisite (item_id from GET /papajohns/india/menu) lives in the schema, not the description, so the agent must cross-reference structured fields to know the call order.

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