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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is covered. The description adds valuable context by specifying the data source, the metrics returned, and the per-call cost, which helps an agent understand expected behavior and output scope.

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 compact and front-loaded with purpose and use cases. The example, source, and pricing each add useful information, but the sentence is somewhat long and could be split for easier scanning.

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 one required parameter, no output schema, and annotations covering the read-only profile, the description provides enough return-value context by listing the included quality measures and data source. It does not specify output shape or handling of ambiguous hospital names, but these are minor gaps for a simple 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 description coverage is 100%, with the single parameter already described as 'Hospital or facility name.' The description adds a concrete example ('Northwestern Memorial') but no deeper parameter semantics such as formatting, aliases, or matching behavior.

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 identifies the tool as returning CMS Hospital Compare quality scores with specific metrics such as safety, readmissions, patient experience, mortality, and star rating. It is differentiated from siblings by naming Hospital Compare data and a broad quality profile, though it does not explicitly call out overlapping tools like get_cms_star_rating.

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 opens with explicit use cases: referral network decisions, acquisition target assessment, and competitive quality analysis. It provides clear context for when to use the tool but does not include exclusions or explicit alternatives.

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