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

Annotations only declare readOnlyHint and openWorldHint; the description adds substantial behavior beyond that — result cap of 100 per search, closest-first ordering, a coverage limitation, and a precise cost model ($0.01 USDC per successful call via x402 on Base/Solana/Arc, with failed calls uncharged). Pricing and coverage caveats are exactly the kind of context annotations cannot convey.

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?

Two sentences, front-loaded with the core verb+resource and outputs before the caveat and price. Dense but every clause carries information; the specialty enumeration ('general practice, orthodontics, endodontics…') is slightly padded but illustrates result shape.

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?

An output schema exists, so return-structure explanation is unnecessary; the description instead covers what that schema cannot — source coverage, result cap, ordering, and payment mechanics. For a paid, read-only directory lookup, an agent has everything needed to decide and invoke.

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 all three parameters (address, limit, specialty) are already documented with examples and defaults. The description reinforces the 100-result cap and closest-first ranking but adds no syntax or format detail the schema lacks, so the baseline holds.

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 ('American Dental Association member dentists near a US ZIP code'), then enumerates exactly what is returned (name, specialties, practice name/address, ADA profile link) and the ordering ('closest first'). The 'ADA members only' qualifier separates it from broader practitioner directories in the sibling list such as b2b_doximity or b2b_webmd_healthcare_provider_directory.

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?

Gives clear preconditions for correct use: a US ZIP (or street address with ZIP) is required, and 'a bare city name returns no cards' is surfaced in the schema. The 'ADA members only; not every licensed dentist is listed' caveat tells the agent when results will be incomplete. It stops short of naming an alternative source when full licensure coverage is needed.

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