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

Annotations already declare readOnlyHint, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: it discloses the empty-result condition when the business does not collect reviews, which matters for interpreting output. It stops short of saying how many reviews 'latest' returns or whether the set is paginated.

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 short sentences with no filler; the core content is front-loaded and the edge case is a single tight clause. Every sentence 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 two-parameter read tool with no output schema, the description covers what is returned (average rating, latest reviews) and the empty case, which is what an agent needs to interpret results. It could be more complete by clarifying the volume or ordering of 'latest' reviews.

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 business and location_id are already fully documented with cross-references to find_business. The description adds nothing about parameter behavior (such as how location_id defaulting affects which reviews are returned), so the 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 resource (average rating plus latest client reviews of a business location) and the context it mirrors (the booking page). It is distinguishable from the sibling list_* tools by domain, though it never names a sibling to contrast with.

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?

Usage is only implied: an agent can infer it should call this when review content is needed for a business/location, but there is no explicit when-to-use, prerequisite, or alternative (e.g., versus get_business, which might also surface rating data).

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