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 one genuinely useful behavioral caveat — that price is only present 'when Zomato's own anonymous response includes one' — flagging unreliable/partial price data, but says nothing about auth, rate limits, or request constraints.

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 tightly written sentence with zero padding; the core resource (menu, grouped by category) is front-loaded and the price caveat is appended as a qualifier rather than a second sentence.

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 structure needn't be explained, and annotations cover the safety profile. For a single-parameter read tool this is nearly complete; only the upstream discovery step is left implicit rather than stated in the description.

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%, so the single url parameter is fully documented in the schema, including its provenance from /zomato/search. The description adds no further syntax or format detail beyond that, which is the correct baseline when the schema does the work.

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: a restaurant's menu, scoped to Zomato India, grouped into categories. An agent can distinguish this from zomato_restaurant (details) and zomato_search (discovery) without opening the schema, 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 tool name and 'restaurant menu' make the intent obvious, and the schema's url description points to /zomato/search as the upstream source. The description itself gives no explicit when-to-use or when-not-to-use guidance versus zomato_restaurant or zomato_collections.

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