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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine non-schema context: 20 facilities per page (pagination size), the field set returned, and that rating values are constrained by another tool. No auth or rate-limit context, but it adds real value over the annotations.

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 search action and scope before the follow-up guidance, and the two sentences mostly earn their place. The enumerated return fields are somewhat verbose given an output schema exists, but overall it is tight and readable.

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 values need not be spelled out, yet the description does so anyway. The real gap is parameter documentation: with 8 params at 0% schema coverage and 6 optional filters unexplained, an agent lacks enough to use the filters (award, sort, rating, distance, query) 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 0% across 8 parameters, so the description carries the full burden. It only clarifies type (facility kind), where (city or ZIP, implied), and rating (indirectly); page, sort, award, query, and distance are left entirely unexplained. Compensation is far from complete.

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 (Search) plus resource (Healthgrades hospitals, pharmacies, group practices, urgent care centers) and scope (near a city or ZIP), with the returned fields enumerated. This distinguishes it from the physician-oriented siblings via the facility types listed, though it never names a sibling explicitly.

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?

'Use type to pick the facility kind' and 'hospital rating values come from healthgrades_facilities_filters' give a usable hint and route to the filters sibling. However, there is no when-to-use guidance versus healthgrades_physicians_search, healthgrades_facility, or healthgrades_locations, so usage is only partially implied.

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