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 useful scoping context by naming the data returned (aggregate rating, review count, recent reviews), but an output schema exists so return details are largely redundant and no freshness/pagination behavior is disclosed.

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 tight sentence that front-loads the resource and parenthetically enumerates the payload. Zero filler; every clause 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 simple one-parameter read tool with full schema coverage, annotations for safety, and an output schema documenting returns, the description is adequate to call it correctly. Only minor gaps (no mention of pagination or review recency limits) remain.

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 the single storeUuid parameter is fully documented in the schema (including that it comes from the search endpoint's storeUuid field). The description adds no parameter meaning beyond that, so the baseline of 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 — a reviews snapshot for a UberEats store — and even enumerates the returned content (aggregate rating, review count, recent reviews). This clearly separates it from siblings like ubereats_store, ubereats_store_menu, and ubereats_search, though it does not name them explicitly.

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 purpose strongly implies when to use it (fetch reviews for a known store), and the required storeUuid makes the precondition obvious, but there is no explicit when-to-use/when-not guidance or mention of alternatives for obtaining review data.

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