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 the result-ordering trait ('nearest first'), which is genuinely beyond the annotations, but says nothing about radius defaults, result caps, or what happens when no stores fall in range — schema covers the bounds only.

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?

A single front-loaded sentence with no filler; scope and ordering come first. The trailing clause 'with the store number kfc_menu and kfc_promotions take' is grammatically garbled and slightly obscures the chaining point, which keeps it from a 5.

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 need not be explained. For a simple geo-search tool, purpose, ordering, and downstream chaining are all covered; only alternative-routing against kfc_stores is missing.

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, occasion, max_results, and radius_miles are already documented in the schema. The description only echoes 'near a coordinate' and adds no format or syntax detail beyond it, so baseline 3 is appropriate.

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 combination — KFC restaurants near a coordinate, sorted nearest first — which separates it from the directory-style kfc_stores sibling. It does not name that sibling explicitly, but the geo+ordering scope is unambiguous.

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 usefully tells the agent what to do AFTER the call — feed the returned store number into kfc_menu and kfc_promotions — which is real chaining guidance. However, it gives no when-to-use/when-not guidance against the many KFC siblings (kfc_stores, kfc_store, kfc_delivery_estimate), leaving the selection condition implied.

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