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

Annotations already signal readOnlyHint=true, and the description adds meaningful behavioral context: coverage is uneven by design and follows where the author has actually eaten. This explains why a missing city is expected rather than an error. It does not describe return formatting, but the basic output shape is clear.

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 description is compact and front-loaded: the first sentence states the main purpose and output, and the second sentence adds a crucial caveat and usage warning. Every sentence earns its place with no filler.

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 parameterless list tool with a read-only annotation, the description is complete. It states what is returned (cities and venue counts), why coverage may seem incomplete, and how to use it correctly. No output schema exists, but the description provides enough return-value detail for safe invocation.

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 input schema has zero parameters, so the baseline is 4. The description correctly focuses on behavior and output rather than parameters, and there is no parameter ambiguity to resolve.

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 names a specific action and resource: 'List every city the Max Eats Out guide covers' and adds the output detail 'with how many venues each holds.' This clearly differentiates the tool from siblings like get_city or get_venue, which focus on individual items rather than the full coverage set.

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 explicit when-to-use guidance: call this before assuming a city is covered, rather than searching a city that is not in the guide and reporting no results. This also conveys a when-not-to-use scenario, which helps an agent avoid false-negative conclusions.

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