cms_nursing_homes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, covering safety. The description adds context about the data types included, which is useful but doesn't disclose rate limits, pagination, or output format. With annotations present, this is a modest additional contribution.

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, front-loaded sentence that states the purpose and key capabilities without any filler. Every clause adds value.

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 data content and mentions state filtering. It doesn't describe the return format, but no output schema exists; however, the listed data types imply what will be returned. Given the annotations and schema, the description is reasonably complete for a query tool, though a note on output structure would make it fully self-contained.

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%, so all three parameters are documented. The description mentions filtering by state, which maps to the state param, but doesn't add detail beyond the schema for the dataset enum or limit. Baseline of 3 applies when schema covers parameters.

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?

States the specific verb 'Query' and resource 'CMS nursing home data', and lists concrete contents (provider info, five-star ratings, quality measures, health deficiencies/citations). It clearly distinguishes from siblings like cms_hospitals and cms_search by focusing on nursing homes.

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?

Provides clear context: this is for querying nursing home data, filterable by state. It does not explicitly mention alternatives or when not to use, but the resource specificity is enough to guide an agent among the many CMS siblings.

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