cms_hospitals

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

Annotations already declare readOnlyHint=true, so the description's behavioral transparency burden is light. It adds context about data types but does not disclose pagination, rate limits, or response format. No contradiction with annotations.

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, focused sentence of 16 words that efficiently captures purpose, scope, and filter criteria. No unnecessary verbiage.

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?

Given the simple structure (4 parameters, 0 required, no output schema), the description covers the essential information: data types and filters. It could be slightly enhanced by mentioning return format or dataset enum, but is largely 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?

Schema coverage is 100% with all parameters described. The description echoes filter capabilities (state/city) and data types, but does not add meaning beyond what the schema already provides, meeting 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?

Description uses specific verb 'Query' and resource 'CMS hospital data', enumerates data categories (general info, quality ratings, mortality, etc.) and explicitly mentions filtering by state or city. This clearly distinguishes it from sibling tools like cms_nursing_homes (nursing home focus) and general cms_query.

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?

Description clearly indicates usage for hospital data and filtering options. However, it does not explicitly contrast with similar tools (e.g., cms_search or cms_query) or state when not to use it, leaving some ambiguity for nuanced selection.

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