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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral detail beyond that: results are ordered nearest-first and the output carries the Olo restaurant_id. It doesn't mention pagination or radius/limit interplay, but the ordering disclosure is real added value.

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?

One tight sentence with zero filler. The resource and ordering constraint are front-loaded, and the downstream linkage is appended economically.

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?

An output schema exists, so return values needn't be spelled out, and the description still highlights the key returned field (restaurant_id). It is essentially complete for a nearby-search tool; only minor behavioral notes like result-count behavior are absent.

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 latitude, longitude, limit, and radius are already fully documented. The description only implies that a coordinate is the input center and adds no format or range detail beyond the schema, so the baseline 3 is correct.

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+resource ('Jimmy John's restaurants near a coordinate') and a distinguishing scope ('nearest first'). It also names the downstream consumer (jimmy_johns_menu) and the field it needs, so an agent can tell this apart from jimmy_johns_store or jimmy_johns_sitemap without opening a schema.

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?

It clearly signals the workflow context by noting it returns the Olo restaurant_id that jimmy_johns_menu needs, which tells an agent when to reach for this tool. It stops short of explicit when-not guidance or naming alternative sibling tools directly.

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