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 useful context beyond annotations: results are paged, and each hospital record carries profile URLs, addresses, and award years, plus the implicit requirement that a valid award value must be obtained from the filters sibling before calling.

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?

One dense sentence that front-loads the verb, resource, and filter list, then appends the return shape and the cross-reference. Nothing is wasted, though the long parenthetical enumeration of award types makes it slightly heavy.

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 explaining return fields was not strictly necessary (though it does). For a 12-parameter tool with zero schema descriptions, the description documents only a subset of inputs, leaving the pagination/sort/geographic parameters to be inferred; adequate but with clear gaps.

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% across 12 parameters, so the description carries real weight and it does name five filter dimensions (year, state, city, specialty, list size) plus the required award. But page, sort, latitude, longitude, ob_gyn_type, and list_category are undocumented anywhere, so it only partially compensates for the coverage gap.

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 (List) and resource (hospitals receiving a Healthgrades quality award), then enumerates the six award families so the agent knows the exact domain. It is clearly distinguishable from the sibling healthgrades_hospital (single facility) and healthgrades_hospital_award_filters (value lookup).

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?

It explicitly routes the agent to healthgrades_hospital_award_filters for accepted award values, which is a real usage instruction. However, it never states when NOT to use this tool (e.g., versus healthgrades_hospital or healthgrades_facilities_search), so the alternative selection is only partially covered.

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