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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is carried by structured data. The description adds essentially nothing behavioral beyond that: it does not state what is returned (names, addresses, ratings), whether results are paginated or capped, or what happens when city is omitted. The affiliation disclaimer is legal boilerplate rather than agent-useful behavior.

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?

It is short and front-loaded, but only two clauses exist and one of them is a non-affiliation disclaimer that consumes roughly half the text. Proportionally, a large share of a very small budget is spent on content that does not help invocation.

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 simple, single-parameter read tool with full annotation coverage and a documented schema, the bar is lower. Still missing is what a result looks like and what an omitted city yields (all restaurants, or nothing), which matters because city is not required and there is no output schema.

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% and the city parameter is already documented with an example format, so the description's "by city" adds nothing new. It also does not clarify the meaningful edge case that city is optional (0 required parameters), which the schema leaves implicit. Baseline 3 applies since 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?

The phrase "Real restaurants by city" identifies the resource (restaurants) and the filter (city), and the tool name supplies the verb. However, it is a sentence fragment that never says it returns a list, and the parenthetical disclaimer dilutes the one clause of purpose. No sibling tool deals with restaurants, so differentiation is not an issue, but the statement of what the tool does is thinner than a precise verb+resource claim.

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?

There is no guidance on when to use this versus anything else, no prerequisites, and no note about the fact that city is optional. The only supplementary sentence is a non-affiliation disclaimer, which does not help an agent decide whether or when to call the tool.

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