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

Annotations already declare readOnly/idempotent/closed-world, so safety is covered. The description adds genuine value beyond that by disclosing the breadth of returned content, including matched FHA-insured HUD 232 loans with note rate, balance, maturity and servicer — context an agent can't infer from annotations. It does not mention behavior when no match is found or that owners may be truncated at max_owners.

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 identifies the lookup key first, then the payload. It is dense but every clause corresponds to real returned data; the loan-detail clause is slightly long but justified given no output schema.

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, the description carries the burden of telling the agent what comes back, and it does so thoroughly across clinical, ownership and loan dimensions. The only gap is not noting the record's owner-list cap or empty-match behavior, which is minor for a read-only lookup.

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%, with both ccn and max_owners fully documented including format, range and how to obtain a CCN. The description adds no parameter-level meaning beyond the schema, so the baseline 3 applies.

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 a specific verb and resource ('One nursing home's SNF Register record by CCN') and then enumerates exactly what that record contains (beds, occupancy, star ratings, staffing, fines, ownership, HUD 232 loans). This clearly distinguishes it from search_nursing_homes and list_hud_232_nursing_home_loans, which operate over sets.

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 'by CCN' framing makes clear this is the single-record detail lookup in contrast to the search/list siblings, so implied usage is strong. It stops short of explicitly naming alternatives or exclusions (e.g. 'use search_nursing_homes first to obtain a CCN'), which the schema description supplies instead.

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