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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by specifying the data source ('CMS Care Compare synced data'), the domains covered, and an example benchmark. This goes beyond minimal annotation coverage and gives the agent useful context about data scope and freshness.

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?

The description is three sentences: use-case guidance, data returned, and a concrete example with source attribution. It is front-loaded with the primary purpose, every sentence adds meaningful detail, and nothing is redundant or wasted.

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?

For a single-parameter, read-only query tool with no output schema, the description adequately conveys what data is returned and at what granularity. It mentions the core measure categories and provides an illustrative example. It could be slightly broader on measure units or timeframes, but given the tool's simplicity, it is sufficiently complete.

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?

The schema already documents 'hospital_name' as 'Hospital or facility name' with 100% coverage. The description adds only that scores are 'by hospital,' which is implicit in the parameter. Since the schema fully explains the parameter, the description does not need to add more and meets the baseline.

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 clearly states the tool returns CMS Hospital Compare scores including safety, readmissions, patient experience, mortality, and star rating by hospital. It uses a specific verb ('Returns') and resource ('CMS Hospital Compare scores'), and the example with Northwestern Memorial concretely illustrates the output. This distinguishes it from sibling tools like get_cms_star_rating by emphasizing a broader multi-domain quality dataset.

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?

The description explicitly lists when to use: 'evaluating hospital quality for a referral network decision, acquisition target assessment, or competitive quality analysis.' It does not explicitly name alternatives or exclusions relative to sibling tools, but the use cases are clear and provide strong guidance on appropriate context.

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