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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description usefully enumerates the returned fields (distance, hours, fulfillment services, payment options, ordering link), but adds nothing about pagination, rate limits, or radius behavior beyond the schema.

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 zero waste; the resource and returned fields lead. The field list is slightly dense but every element earns its place.

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 read-only nearby-search tool with a fully documented schema and an existing output schema, the description supplies enough to call it correctly. Return-format detail is unnecessary since the output schema exists.

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 already fully documented. The description only restates the lat/long center and adds no format, range, or unit nuance beyond the schema, so 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?

States a specific verb and resource ('proximity search: stores near a latitude/longitude') and enumerates the data returned. It is distinguishable from siblings like papajohns_directory or papajohns_store, though it never names an alternative to disambiguate.

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 proximity framing implies when to use it (finding stores by coordinates), but there is no explicit when/when-not or reference to sibling tools such as papajohns_store or papajohns_directory. Usage is inferable but not guided.

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