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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description goes beyond that by disclosing the returned structure (combo slots, quantity/size/skip rules, eligible items, rupee pricing), which helps the agent know what it gets back. It adds no auth or rate-limit context, so not a 5.

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, the primary action front-loaded and the routing hint placed second. Every clause carries information; no padding.

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 1 param fully documented, an output schema, and readOnly annotations, the description plus structured fields cover everything needed to call the tool correctly. Return-value detail is a bonus rather than a 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 schema already explains deal_id's origin (items with kind=deal from the menu endpoint). The description only echoes 'by deal_id' without adding format or edge-case detail, so the baseline 3 for schema-complete parameters 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 (Fetch one), resource (Papa John's India deal), identifier (deal_id), and enumerates the payload (combo slots, quantity/size/skip rules, eligible items, prices in INR). It reads distinctly from sibling menu tools.

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?

Explicitly routes the agent: use papajohns_india_menu to browse items, papajohns_india_menu_item for a single item, implying this tool is for deal retrieval. Alternatives and their purposes are named, leaving nothing to inference.

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