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

Annotations already declare readOnlyHint and openWorldHint, so the description's real contribution is the billing model: $0.002 USDC per successful call via x402 on Base/Solana/Arc, with failed calls not charged. That is precisely the kind of cost/behavioral context an agent needs before calling a paid, open-world scraper. It stops short of latency, rate limits, or partial-result behavior.

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?

Purpose is front-loaded and every clause is information-dense, with pricing placed last where it belongs. The long enumeration of ~15 returned fields is somewhat wasteful given an output schema exists, making the single sentence heavier than necessary.

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 annotations covering the safety profile, a full output schema covering return values, and a 100%-described input schema, the description only needs to add cost and scope — which it does. An agent has enough to decide, pay, and call 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?

Schema description coverage is 100% and the schema already spells out city, state, limit range, and example specialty slugs, so the description adds little beyond restating the specialty list and the 20-provider cap. Baseline 3 is appropriate; it does not explain slug format rules beyond what the schema provides.

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 the specific resource (doctors), the source (Healthgrades' specialty directory), the geographic scope (near a US city), and the cap (up to 20 providers). This also disambiguates the odd tool name, which sits among real-estate siblings but actually returns provider records.

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?

Usage context is implied by the required inputs (US city + state + specialty slug) and reinforced by the sample specialties, so an agent can infer when this applies. However, it gives no explicit when-to-use/when-not guidance, no statement about coverage limits (US only, no radius parameter), and no routing to any alternative source.

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