cms_hospitals

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 the data categories but doesn't disclose behavioral traits like pagination, rate limits, or what happens with no filters. It provides some context beyond annotations but not rich behavioral detail.

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 a single, well-structured sentence. It front-loads the purpose ('Query CMS hospital data'), then lists the data categories and filters without any redundant or vague wording.

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?

The description covers the core purpose and filter options but doesn't mention the default dataset (hospital_info) or the default limit (50), which are in the schema. It also doesn't describe the response format, though there is no output schema. For a query tool with optional parameters, this is adequate but not comprehensive.

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 all four parameters (city, state, limit, dataset) have descriptions. The description reinforces the state/city filtering and lists the dataset categories, but it doesn't add meaning beyond what the schema already provides. The enum values are self-explanatory.

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 queries CMS hospital data and lists specific data categories (quality ratings, mortality, readmissions, infections, patient surveys, Medicare spending). This distinguishes it from cms_nursing_homes, but it doesn't explicitly differentiate from the generic cms_query tool, so it's not a full 5.

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 mentions filtering by state or city, which implies usage when hospital data is needed. However, it doesn't explicitly state when to prefer this over sibling tools like cms_query or cms_nursing_homes, and no alternatives are named.

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