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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: it states which fields come back, that locations are included, and notably that patient-authored review text is omitted, which prevents a failed expectation. It does not mention rate limits or pagination.

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 tightly packed sentences with zero filler. Return scope is front-loaded, followed by the input prerequisite and the omission caveat, in that order.

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, return values need not be enumerated, and the description still covers what is returned, what is excluded, and the input requirement. Only the routing to a discovery tool for obtaining the URL is left implicit.

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 there is only one parameter, so the schema already carries the load. The description reinforces the 'canonical' URL constraint but adds no format, casing, or example beyond what the schema states, matching the baseline 3.

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 pairs a specific verb ('Returns') with a precise resource ('public professional fields and practice locations from a Healthgrades physician profile'). This distinguishes it from siblings like healthgrades_physicians_search and healthgrades_facility, but it never names an alternative explicitly, so it stops short of a 5.

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?

Stating it 'Requires a canonical Healthgrades physician profile URL' implies the agent must resolve a URL first (e.g. via healthgrades_physicians_search), but no explicit when-to-use or alternative tool is named. Usage is only implied.

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