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

Annotations already establish read-only, non-destructive, open-world access, and the description adds real behavioral context: cursor vs. offset paging, the requirement to keep other filters fixed across pages, the hasNextPage termination condition, and the fact that notRecommended reviews lack photos/videos/reactions. No rate limits or auth requirements are mentioned.

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?

It is front-loaded with purpose, then pagination mechanics, then the response shape, then use cases. It is longer than average but each block carries information; the closing use-case list is the most expendable part.

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 ten parameters and no output schema, the description does the right thing by describing the returned review fields, business rating/language totals, and pagination echo fields. Combined with the exhaustive schema, an agent has what it needs to call it correctly.

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%, so the schema already documents every parameter in detail, including the rating/query interaction and the start vs. nextPageToken exclusivity. The description mostly restates these at a higher level (sort modes, star filter, language, free-text, cursor), adding little beyond the schema.

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 and resource ("Fetches the review feed of a single Yelp business by Yelp ID") and enumerates the supported sorting and filtering axes. It is clearly distinct from a place-details or search tool, though it does not name the siblings 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?

It gives concrete usage contexts at the end (sentiment monitoring, competitor complaint mining, owner-response tracking, rating-distribution datasets) and a precise pagination procedure. It stops short of stating when to prefer the sibling search or place-details tools instead.

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