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 real context by disclosing the shape of the payload (awards with years, service-line ratings, patient-experience measures), though some of that overlaps with the output schema. No contradictions.

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 sentences, no filler, and the core purpose plus payload contents are front-loaded before the usage hint. Every clause earns its place.

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 single-parameter read tool with an output schema and full annotation coverage, the description supplies what structured fields cannot: the prerequisite search call and the distinguishing content. It is complete enough to invoke correctly, with only minor overlap into return-value territory the output schema already owns.

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 100% and there is only one parameter, whose schema description already states it comes from /healthgrades/facilities/search. The description's "by URL" adds nothing beyond the schema, so the 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 verb and resource ("Get a Healthgrades hospital profile by URL") and immediately enumerates the substantive content returned (awards with years, clinical outcome ratings by service line, patient-experience measures, address, phone). This distinguishes it from the broader healthgrades_facility and from healthgrades_hospital_awards without opening any schema.

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 after healthgrades_facilities_search with type=hospital" gives an explicit prerequisite and the exact parameter needed to reach this tool, which is genuinely actionable. It stops short of naming when NOT to use it or an alternative for other facility types, so it lands short of a 5.

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