How far to trust each hospital's price file

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds interpretive context about what 'quality' comprises, but that content is largely a preview of the return payload (which an output schema already supplies) and says nothing operational such as data freshness, staleness, or cost of the call.

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 'Per hospital' scope, then the usage cue. The itemized list of quality dimensions is dense but earns its place; the parenthetical '(and how often)' is slightly clunky but informative.

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 present, the description needn't detail return values, and the single parameter is documented. Annotations cover side effects. The remaining gap is the absence of any routing guidance relative to the five sibling tools.

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 the single hospital_id parameter is fully documented in-schema, including the enum values and the 'omit for all three' default. The description never mentions the parameter, so it adds nothing beyond the schema — 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?

The description enumerates exactly what the tool returns per hospital: NPI-to-NPPES resolution, undisclosed NPI counts, CMS-template departures with frequency, and quarantined rows. That is a specific, recognizable 'data quality/provenance report' distinct from price-lookup siblings like compare_code_prices and get_payer_rates. It stops short of an explicit verb framing (e.g. 'Assess the quality of...'), but the resource and scope are unambiguous.

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 it to qualify any price answer' gives a clear, actionable context for invoking the tool. There is no statement of when NOT to use it and no named alternative among the siblings, so it falls short of a full 5.

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