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

Adds substantial behavior beyond annotations: up to 100 results, closest-first ordering, ADA-members-only coverage limits, a $0.01 USDC cost per successful call, x402 payment methods, and failed calls not charged. These are important operational details an agent could not infer from readOnlyHint/openWorldHint alone.

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?

Front-loads the resource and scope, then adds coverage caveats and pricing. It is dense but efficient; the long field enumeration is useful, though slightly bulky.

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?

Given the output schema, annotations, and 100% parameter coverage, the description supplies the remaining operational context: source, coverage limits, ordering, result cap, and payment behavior. Nothing critical for correct invocation is missing.

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 every parameter is documented in the input schema, including limit, address reliability, and specialty examples. The description reinforces ZIP-code usage but adds little beyond the schema, so baseline 3 is appropriate.

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 resource and scope: American Dental Association member dentists near a US ZIP code, with the exact returned fields and closest-first ordering. It distinguishes itself from generic provider directories by emphasizing ADA members only.

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?

Provides clear context that this is for ADA member dentists near a US ZIP code, and notes members-only coverage, but does not explicitly compare against siblings like WebMD, Healthline, Doximity, or Google Maps. The when-to-use case is implied rather than spelled out.

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