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

With no annotations, the description carries the full behavioral burden but discloses almost nothing. It never defines the ranking criterion, whether results are cached/live, how many are returned by default, or how the limit interacts with "top" selection; only the noun phrase hints at a read-only collection.

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 fragments with no wasted words and the resource is front-loaded. However, this brevity comes from under-specification rather than disciplined editing, so it is concise but not informative.

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 tool with no annotations and no output schema, and with ~40 sibling tools competing for selection, the definition should at minimum define the ranking basis and route between alternatives. Neither is present, leaving the agent to guess whether to call this or get_top_venues/get_local_gems.

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 nominally 100%, so the baseline is 3, but the schema "descriptions" are placeholder-level ("city", "limit") and convey no real meaning. The description confirms city is optional yet never mentions limit or its effect on the "top" ranking.

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?

"Top restaurants" essentially restates the tool name in prose and adds no criteria for what "top" means (rating, popularity, editorial). It does not differentiate from siblings such as get_top_venues, get_local_gems, or get_locals_favorites, which an agent would need to distinguish among.

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?

"Optional city" is the only usage signal, and it merely restates that city is optional. There is no when-to-use guidance, no mention of alternatives, and no indication of when this should be preferred over the many other place-listing siblings.

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