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

With no annotations, the description carries the full behavioral burden. It discloses the data source (CMS), the breadth of the scorecard, and the comparison methodology (better/same/worse vs national average), and read-only lookup is strongly implied by 'scorecard' and 'Look up'. It does not state behavior for unknown IDs or names, whether results are cached/rate-limited, or what happens when multiple hospitals match a name.

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?

Single dense sentence that front-loads the resource and its returned fields, then closes with the lookup modes and disclaimer. Every clause carries information, though splitting the returned-fields list from the lookup instruction would improve scanability.

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?

There is no output schema and no annotations, so the description must describe returns itself — and it does, covering ratings, comparisons, and rank/percentile. Combined with 100% parameter coverage, the only remaining gap is edge-case behavior (no match, ambiguous name) which is a minor omission for a lookup 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 100%, so the baseline is 3, but the description adds real semantics beyond the schema by specifying the acceptable lookup combinations (ID alone, or name together with state) — a coupling the flat schema does not express. It does not clarify what happens when only name is supplied without state.

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 concrete verb and resource ('Hospital scorecard for any U.S. Medicare hospital') and enumerates the returned content: CMS star rating, type, ownership, emergency services, national-average comparisons, and state rank/percentile. An agent can immediately tell this apart from health_drug_label, health_recalls, or travel_advisory.

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?

Gives clear lookup guidance ('Look up by CMS facility ID or name plus state') and scopes the domain to U.S. Medicare hospitals, with a 'Not medical advice' boundary. It stops short of naming when not to use it or pointing at close alternatives such as health_hospitals, so sibling routing is left to inference.

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