zomato_collection

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

With no annotations, the description carries the burden, and it discloses the returned fields and the conditional nature of the review count ('where Zomato's own response includes them'). It also explains the underlying source relationship. It could say more about error cases or pagination, but for a read-style lookup the behavioral profile is reasonably transparent.

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?

The two-sentence description is short and front-loaded, but the first sentence ('Get one...list') is almost fully repeated by the second. It earns most of its value from the parenthetical field list and the source caveat, yet the redundancy keeps it from being tight.

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 tool with no output schema, it explains what comes back (name, cuisines, locality, rating, review count) and when a field may be absent. The schema covers URL provenance, and the sibling contrast covers selection. The main omissions are pagination/limits and explicit collection-list guidance, but these are minor for this scope.

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?

The only parameter, url, is already 100% documented in the schema, including the requirement that it come from /zomato/collections's url field. The description adds no additional parameter-level detail, so the baseline of 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?

The opening sentence names the exact operation: retrieve one curated collection's restaurant list. The description further separates it from the restaurant-detail siblings by stating it points at the collection's own page rather than a restaurant's page.

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?

It explicitly positions itself against /zomato/restaurant and /zomato/restaurant/menu by saying it reads the same page-render source but for a collection page. It does not spell out 'use this when you already have a collection URL' or contrast with /zomato/collections, but the schema's URL provenance covers that.

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