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 adds genuine behavioral context beyond that: the menu is priced per restaurant, includes every priced size/crust/style variant, and combined with the channel parameter implies prices vary by ordering channel.

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 core scope (one restaurant, full priced menu) before listing the enrichment detail. No filler, though it could be split for scannability.

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 output schema present, the description doesn't need to explain return values, and the annotations cover safety. The description's note about categories and variant pricing rounds it out; only the lack of guidance on sibling selection keeps it from a 5.

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% — store_number's provenance (/pizzahut/stores) and channel's full enum list and default are documented in the schema. The description adds nothing parameter-specific, 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?

Specific verb+resource: retrieves the full priced menu for a single Pizza Hut restaurant, grouped into categories, with price/image/variant detail. This clearly separates it from pizzahut_stores (store listing) and pizzahut_modifiers, though no sibling is named explicitly.

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: the required store_number signals that you need a store identifier first, but the description never states when to call this versus pizzahut_modifiers, pizzahut_bundle_choices, or pizzahut_store, nor any prerequisite like looking up the store number first.

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