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 that it is a location-driven feed requiring coordinates, but discloses nothing further about pagination, result volume, or coverage limits. Adequate but thin beyond the annotations.

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?

Three short sentences, front-loaded with the identity of the tool and followed by the differentiator and the required inputs. Little waste, though the final sentence is largely redundant with the schema's required array.

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, return values need no explanation, and read-only annotations carry the safety profile. Purpose, contrast with siblings, and inputs are all covered; only behavioral depth (result shape, limits) is left implicit.

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 coverage is 100% and both parameters are required, so the schema already documents latitude and longitude. The sentence 'Requires latitude and longitude' only restates the required list without adding format, range, or coordinate-system meaning. 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+resource+scope: 'DoorDash location-based nearby stores explore feed.' It explicitly names the sibling tools it is not (search, autocomplete), so an agent can differentiate it without opening either 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?

Gives a clear selection condition: use this when no search query exists, unlike search/autocomplete. It stops short of stating the inverse rule (use doordash_search when you do have a query) and mentions no other exclusions, but the routing intent is unambiguous.

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