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 results are paged and include profile URLs, addresses, and award years, which is useful behavioral context, though with an output schema present the return detail is partly redundant.

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-loaded with the core purpose, then filter dimensions, then the sibling routing hint. Two efficient clauses with no filler, though the parenthetical award enumeration makes the first sentence dense.

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, 100% parameter coverage, and annotations, the description only needs to frame purpose and routing, which it does. The sibling pointer for accepted values closes the main gap; behavior under sort/distance is left entirely to the schema.

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%, so the baseline is 3. The description names the filter axes (year, state, city, specialty, list size) but adds no syntax, defaults, or dependency rules beyond what the schema already documents.

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 that received a Healthgrades quality award'), then enumerates the award types and the filter dimensions. An agent can distinguish this from siblings like healthgrades_hospital or healthgrades_hospital_award_filters 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?

Explicitly routes the agent to healthgrades_hospital_award_filters for accepted values, and lists the filter dimensions. It gives clear context but stops short of stating when NOT to use this tool versus the facility/hospital search tools.

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