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

The annotations already declare readOnlyHint=true, so the description does not need to restate safety. It adds useful behavioral context beyond the schema: the Infatuation rating scale, strict rating ordering, and the implicit no-free-text constraint. This is more than a bare read, but it does not disclose pagination or error conditions (though those are partly in schema).

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?

Three sentences, front-loaded with the core action and scale, then a clear usage directive, then a differentiation note. No wasted words; every sentence earns its place.

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?

Given the tool has 11 parameters but a fully descriptive schema, and annotations cover read-only behavior, the description provides the essential extra context (scale and ordering). Nothing needed for correct invocation is missing—the lack of an output schema is acceptable for a list tool.

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 schema already documents every parameter in detail. The description mentions 'cuisine, neighbourhood and price filters' but adds little beyond the schema; the scale reference ties to min_rating, but overall it does not compensate beyond the baseline for high coverage.

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 description states a specific verb ('List'), a clear resource ('highest-rated restaurants'), and the rating scale (Infatuation 0–10). It also explicitly distinguishes itself from the sibling search_restaurants by noting the absence of free-text query and strict rating order, so an agent can immediately tell it apart.

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 an explicit use case ('Use for "best in the city" requests') and names the key alternative (search_restaurants) along with the differentiating condition. This tells the agent when to choose this tool over its closest sibling without ambiguity.

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