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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses pagination behavior (10 reviews per page), language filtering semantics (original language, not translation), and the effect of combining language with sort_by. It also mentions billing implications indirectly via the pages parameter description. It does not disclose rate limits or failure modes, but the disclosed behaviors are meaningful and non-obvious.

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 three sentences and front-loads the core purpose. The first sentence states the verb, resource, and key input. The second adds return contents and pagination. The third explains language filtering and the sort_by tip. Every sentence earns its place, though the third sentence could be slightly tighter.

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 7-parameter tool with no output schema and no annotations, the description covers the main behavioral aspects: what is returned, pagination, language filtering, and sort_by interaction. It doesn't describe the output structure in detail, but the absence of an output schema makes that a minor gap. The description is sufficient for an agent to call the tool correctly for common use cases.

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 the baseline is 3. The description adds value beyond the schema by explaining the practical effect of the language parameter (filters to original language, not translated) and the strategic tip to combine language with sort_by. It also clarifies the pagination/billing relationship. This exceeds the baseline but doesn't fully explain all parameter interactions.

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 clearly states the tool retrieves user reviews for a Google Maps place by place_id, and enumerates the review contents (rating, text, author info, timestamps, photos, owner response). It distinguishes itself from siblings like place_details and place_photos by focusing specifically on reviews, and from facebook_page_reviews/trustpilot_company_reviews by naming the Google Maps place context.

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 gives concrete usage guidance: it explains pagination (up to 10 reviews per page), how the language parameter filters reviews, and recommends combining language with sort_by to surface a larger pool. It does not explicitly state when not to use this tool versus place_details or search_places, but the context is clear enough for an agent to select it for review retrieval.

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