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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds value beyond that by disclosing the return content — cuisine names plus per-cuisine branch counts — which is important since no output schema exists. It omits ordering or pagination behavior, keeping it below a 5.

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 short sentences with no filler: the first defines the resource and its payload, the second states the intended use. The purpose is front-loaded and nothing is redundant.

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 zero-parameter enumeration tool with no output schema, the description covers what the list contains and how to consume it, which is essentially everything needed. Minor gaps remain around result ordering and exact response shape (e.g., whether counts appear alongside names), but these are unlikely to block correct 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 tool takes zero parameters and the schema has no properties, so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies, and the description correctly spends no words on parameters.

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?

States a specific verb and resource ('Lists the cuisines a restaurant can be filed under') and adds the distinguishing payload detail that each entry includes how many listed branches name it. The second sentence ties it to search usage, so an agent can immediately tell it apart from list_places, get_restaurant, and search_restaurants, which operate on restaurants rather than the cuisine vocabulary.

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?

Gives explicit downstream guidance: 'Use a name from it as the cuisine of a search,' which tells the agent this is the enumeration step that precedes a filtered search. It stops short of naming search_restaurants outright or stating when not to call it (e.g., when the agent already knows valid cuisine values), so it is strong but not exhaustive.

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