bbb_business_reviews

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

With no annotations present, the description carries full behavioral disclosure burden, and it does this well. It explicitly states credential-free access, pagination at 10 per page, that browser impersonation is used rather than plain HTTP, and references the family maintenance note for further context. This gives an agent important runtime expectations beyond the 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?

The description is compact and front-loaded: it states purpose first, then return contents and pagination, then the important credential and fetch-method caveat. Every sentence contributes useful information without repetition or filler.

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 two-parameter tool with no output schema and no annotations, the description is remarkably complete. It covers the input source, pagination behavior, response contents, credential requirements, and a notable implementation difference (browser impersonation). An agent has enough context to select and invoke this tool correctly.

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 documents both parameters with 100% coverage, so the baseline is 3. The description adds meaningful provenance guidance for the url parameter ('from a bbb-search result's url or hq_profile_url') and reinforces pagination semantics via '10 per page'.

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 a specific resource ('Better Business Bureau business's customer reviews'), and it clearly enumerates what is returned: author, star rating, date, text, business response thread, pagination, average rating, and total count. It also distinguishes itself from the broader bbb-business-* family by noting its unique browser-impersonation fetch method.

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 clearly signals this is the tool to use when a business's customer reviews, review summary, or paginated review history is needed. It also notes the credential-free public nature and differentiates this endpoint from other bbb-business-* calls, though it does not explicitly list exclusions or alternative sibling tools.

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