cms_nursing_homes

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

Annotations declare readOnlyHint: true, and the description's 'Query' verb aligns with that. The description adds content scope (ratings, quality, deficiencies) and a filtering hint, but it doesn't disclose behavioral traits like pagination, rate limits, or result size. It does not contradict 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?

A single sentence under 20 words, front-loaded with the verb and resource. Every word is relevant and there is no filler.

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 no output schema and three optional parameters, the description gives a general overview but doesn't explain how the dataset parameter changes the result shape, whether results are lists or records, or how the listed content areas map to the three dataset enum values. It is adequate but has clear gaps.

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 descriptions for all three parameters, including an enum for dataset. The description adds a mention of state filtering and a high-level summary of data categories, but that is only marginal value beyond the schema's own descriptions.

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's purpose as querying CMS nursing home data with specific content areas (five-star ratings, quality measures, health deficiencies/citations). It distinguishes the resource from sibling tools like cms_hospitals but does not explicitly name alternatives or contrast with generic cms_search.

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 implies use when nursing home data is needed, but it provides no explicit guidance on when to choose this tool over siblings such as cms_hospitals or cms_search. There are no exclusions or alternative tool references.

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