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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description earns credit for adding non-obvious behavior: locations lacking a Reputation Manager report (BrightLocal Grow plan) return zeros plus a note, which tells the agent how to interpret an all-zero result instead of treating it as an error.

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?

Front-loaded with the core purpose and effect, then enumerates the returned metrics. The second sentence is a dense run-on list of every time window (last 30 days, this and last month, this year), which is informative but could be tightened without losing meaning.

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?

No output schema exists, and the description compensates fully by enumerating the return shape: average rating, total reviews, per-star counts, per-site breakdown with links, and the zero-response edge case. For a single-parameter read tool this covers everything needed to call and interpret it.

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?

Only one parameter, documented at 100% coverage in the schema with a direct pointer to list_locations as its source, so the schema already carries the semantics. The description adds no further constraint on location_id beyond the incidental note that some locations have no reputation report; 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 and resource ('Read a location's star rating and review counts') and scopes it as an aggregate summary 'overall and per review site', which implicitly separates it from the sibling list_reviews that returns individual reviews. It stops short of naming that sibling explicitly, so the differentiation is inferable rather than stated.

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 implied by the phrasing ('Read a location's...') but there is no explicit when-to-use, when-not, or alternative-tool guidance. An agent must infer that this is for aggregate reputation metrics and not for fetching individual review text or review response workflows.

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