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

Annotations cover the safety profile (readOnlyHint, openWorldHint), and the description adds genuine content context: the menu is full-priced, grouped by category, and carries both delivery and pickup pricing plus nutrition and allergen flags per item. That tells the agent what kind of data it will receive beyond a generic 'read'.

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 well-formed sentence that front-loads the resource and then enumerates the payload. No padding, though the content list is dense enough that it approaches cramming.

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 an output schema present, the description need not detail return fields, and it still summarizes the payload categories. Combined with a fully described 2-parameter schema, an agent has enough to call this correctly.

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 both market and store_id are fully documented in the schema with defaults and provenance. The description adds nothing about parameters, which is acceptable at the baseline when the schema does the heavy lifting.

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 resource (the Burger King full priced menu) and its shape: categories, delivery/pickup prices, nutrition facts and allergens. It is clearly distinguishable from burgerking_product (single item) and burgerking_locations (store lookup), though it never names those siblings 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?

The description gives no when-to-use guidance. It does not say to call this once per store, nor when to prefer burgerking_product for a single item instead of the whole menu. The store_id provenance hint lives in the schema, not here.

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