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

Annotations already establish readOnlyHint and openWorldHint, so the safety profile is covered; the description still adds real value by disclosing scope limits ('public listings only; no complaint details'), terms-of-service constraints, and the paid-call behavior including that failed calls are not charged. The only gap is that it does not describe pagination or result-volume behavior beyond the limit parameter.

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 useful core (source, lookup method, returned fields, scope limits) is front-loaded in the first two sentences, with routing and pricing trailing. The sibling and payment sentences are somewhat dense with repeated 'when you need' phrasing, but each still carries routing or cost information an agent needs.

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 an output schema present, the description need not explain return values, and annotations cover read-only/open-world behavior; the description nonetheless covers source, scope, licensing, and cost. For a simple two-parameter lookup, what remains missing is minor (pagination/result-limit interaction and error/failure modes beyond billing).

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%, with both q and limit documented including length and range constraints, so the schema carries the parameter burden. The description only restates that lookup is by business name and adds no syntax, matching behavior, or format nuance beyond that; 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?

The description names a specific source (bbb.org public search JSON), a specific verb+resource (finds businesses by name), and enumerates the returned fields (city, state, category, BBB rating, membership flag, profile URL). It also explicitly differentiates itself from the two sibling tools it mentions, so an agent can route without opening a schema.

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 gives clear routing guidance for the adjacent use cases: b2b_bizquest for businesses for sale and b2b_booksy for beauty/barber/wellness listings, both framed as 'for a different need'. It stops short of distinguishing itself from the many other business-directory siblings (e.g. b2b_yellowpages, b2b_manta), and offers no explicit when-not-to-use condition beyond the source-scope note.

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