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 that awards include years and lists the categories returned, but says nothing about auth, rate limits, or pagination. Adequate against the lowered bar but not rich.

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, front-loaded with the action and resource, followed by the return summary and the workflow hint. Efficient, with no wasted prose.

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 format need not be restated, and annotations carry the safety profile; the description supplies the workflow prerequisite and output preview. Complete enough for a single-param read tool.

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 0% and the single required param has no schema description, but "by URL" does signal what the url argument is. It adds no format example or sourcing detail beyond that baseline hint.

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") and enumerates what is returned (awards with years, ratings, patient-experience measures, address, phone). It implies hospital-specific scope versus the generic healthgrades_facility sibling, though it never explicitly contrasts them.

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 clear workflow context and names the preceding tool plus the exact parameter value that routes here. It stops short of stating when NOT to use it (e.g. non-hospital facilities).

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