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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/access profile is covered. The description adds one genuinely useful behavioral fact beyond the schema: no DoorDash account or token is required and results are location-scoped. It does not describe pagination, review ordering, or volume, so value-add is moderate.

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?

Two tight sentences that front-load the purpose and then the required inputs and auth note. Nothing is wasted, though it stops short of a directive statement of when to prefer this over siblings.

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 not be explained, and annotations carry the read-only/open-world profile. For a simple 3-param, all-required lookup tool the description is close to complete; only routing guidance against sibling store tools 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 all three parameters are already documented in the schema. The description restates the required parameters but adds no format, range, or coordinate convention beyond what the schema provides. 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 names a specific verb+resource: retrieving DoorDash store ratings and customer reviews, plus reinforcing the location-aware nature. It does not, however, distinguish itself from closely related siblings like doordash_store, doordash_store_info, or doordash_store_item, so an agent must infer the boundary. Clear purpose, missing sibling differentiation.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative (e.g., doordash_store_info for non-review data). The only usage signal is the statement that storeId, latitude, and longitude are required, which is implied context rather than routing guidance.

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