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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the paid-call economics ($0.002 USDC per successful call via x402 on Base, Solana or Arc, failed calls not charged), the page size (50) and cursor mechanics, and the caveat that some fields appear only 'when listed'. That is exactly the operational context annotations cannot carry.

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?

Three sentences, each front-loading its point: source and modes first, field inventory second, cost and pagination last. No filler, and the pricing/charging caveat is stated compactly rather than padded.

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 zero-required-param, three-parameter lookup with an output schema, the description covers everything an agent needs before calling: which mode each parameter triggers, what a page contains, how to continue pagination, what happens with missing fields, and what the call costs. Return-value structure is correctly left to the output schema.

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 coverage is already 100%, so the schema documents all three parameters, but the description still adds meaning: it pairs `profile` with the two accepted slug/URL forms, `location` with the state/city slug format plus a worked example, and ties `after` to the returned next-page cursor. That is modest added value on top of a fully documented schema.

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 resource and scope: US clinician data from Doximity's public directory, then splits it into two concrete retrieval modes (single profile vs. location listing) with the exact fields each returns. It never explicitly contrasts itself with neighboring clinician directories like b2b_webmd_healthcare_provider_directory or b2b_healthline_medical_providers_directory, so an agent must infer the distinction from the source name.

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 is clearly implied by the input shape: 'By profile (slug or doximity.com/pub URL)' versus 'By location (state or state/city, e.g. north-carolina/raleigh)', which tells the agent which mode each parameter selects. It stops short of explicit when-not guidance, such as what to do if a clinician is not in the directory or why to pick this over a sibling provider directory.

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