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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established without description-level detail. The description adds dataset scope and return-field context, but it does not disclose additional operational behavior such as pagination behavior, rate limits, or query constraints. There is 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?

Two sentences with no filler: the first states the resource and what is returned, and the second states the available filters. The most important identifying information is front-loaded, making the description easy to scan and act on.

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?

For a read-only search tool with all-optional parameters and full schema coverage, the description sufficiently covers what the tool returns and how to filter results. Since there is no output schema, the explicit list of returned fields is valuable, and nothing essential for invoking the tool correctly appears to be missing.

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 five parameters are already documented in the input schema. The description's filter statement loosely restates state, city, and name_contains but does not add meaningful new semantics beyond the schema. The baseline of 3 applies because the schema carries the parameter-documentation burden.

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 opens with a specific action and resource: 'Search Medicare-certified hospitals' from the CMS Hospital General Information dataset. It lists concrete returned fields and filter dimensions, and the hospital focus clearly distinguishes it from sibling CMS facility searches such as cms_home_health_search and cms_nursing_home_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 makes the use case clear: use when the target is Medicare-certified hospitals, filtering by state, city, or partial facility name. It does not explicitly name alternatives or exclusions, but the dataset and resource type are unambiguous enough that an agent can infer when this tool applies versus related CMS facility tools.

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