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 by structured data. The description adds the upstream source ('Yext's Answers API') and a detailed enumeration of returned fields, which is useful context, but discloses no operational traits such as rate limits, result caps, or freshness. With annotations carrying the safety burden, this is a solid-but-unremarkable 3.

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 a single sentence and front-loads the purpose well, which is a plus. However, it then spends the bulk of its length enumerating twelve-plus returned fields (address, phone, hours, price tier, amenities, URLs, Place id, distance) even though an output schema exists — that is repetition of structured data rather than value-adding concision.

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?

With an output schema present, the description need not explain return values, and annotations cover mutability; the core 'what this does' is complete. The remaining gap is the lack of any routing or pagination/intent guidance versus sibling location tools, which keeps it out of the top band.

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 limit, offset, radius, latitude, and longitude are all documented with types, ranges, and defaults in the schema. The description only implies radius ('within a radius of a lat/long') and mentions distance units in the output, adding nothing about the input parameters that the schema doesn't already say. Baseline 3 applies.

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+resource: 'Five Guys restaurants within a radius of a lat/long via Yext's Answers API.' That is unambiguous and tells an agent exactly what the call returns. It does not, however, differentiate from close siblings like fiveguys_search, fiveguys_directory, or fiveguys_ordering_locations, so an agent cannot tell from the text alone which of these nearby/location tools to pick.

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?

Usage is implied rather than stated: the required lat/long pair signals 'use this for geographic proximity lookups.' There is no explicit when-to-use/when-not guidance and no mention of the alternative sibling tools (fiveguys_search, fiveguys_directory) that also return restaurant data. Adequate but leaves routing to inference.

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