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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety is covered. The description still adds real behavioral context: only published reviews are returned, and the payload contains ratings and review text — important since there is no output schema.

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?

Three short sentences, zero filler, with the resource and scope stated first and the exclusion last. Every sentence carries distinct information (what it returns, where the id comes from, what it excludes).

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 no output schema, the description usefully characterizes the return content (ratings and review text). It covers scope, id provenance, and return shape; only minor details like pagination behavior or review ordering are unaddressed, and the limit bound is already in the schema.

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% and the schema already documents both parameters, including the 'rls_...' example that the description repeats. The description adds no new meaning for the limit parameter or the id format beyond what the schema states, 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 and resource: retrieving published customer reviews for a rental listing. It also draws a scope boundary ('Sale listings do not have reviews') that separates it from the marketplace/camper siblings. It stops short of naming a sibling tool directly, so it is clear but not maximally differentiated.

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 tells the agent where the required id comes from ('id from search results') and when the tool does not apply ('Sale listings do not have reviews'), which is useful implied usage guidance. However, no alternative tool is named for the sale-listing case, so the routing is left to inference.

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