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

Annotations already declare the tool as read-only, idempotent, non-destructive, and open-world. The description adds the key scoping detail (by slug, optionally filtered by targetId), but does not disclose behaviors such as pagination limits or response structure. This provides some additional context but not rich behavioral detail beyond annotations.

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?

The description is a compact two-sentence statement that front-loads the verb and object. There is no redundant wording; both sentences provide necessary scope information.

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 read-only tool with two well-documented parameters and clear annotations, the description adequately conveys the purpose and return content (aggregate rating and reviews). It lacks output schema but the description directly states what is returned, making it complete for this complexity level.

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?

The input schema already provides descriptions for both slug and targetId, with 100% coverage. The description's phrase 'Optionally filter to a product/service id' mirrors the schema's targetId description without adding new semantic meaning, so the baseline score 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?

The description uses a specific verb ('Get') and identifies the resource ('a business's aggregate rating and reviews by slug'), clearly distinguishing it from sibling tools like get_business or get_item. The optional targetId filter is also stated, confirming the tool's scope.

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 description implies use for retrieving reviews/ratings but does not explicitly state when to prefer this tool over alternatives such as get_business or get_item. There are no exclusions or alternative tool mentions, so guidance is limited to an implied use case.

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