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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value by enumerating exactly which metrics come back (occupancy, star spread, turnover, PE/REIT flags, HUD 232 activity), which tells the agent what data it gets. It says nothing about aggregation method, time window for "recent ownership changes," or result shape.

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?

One dense sentence that front-loads the scope (state or US) before the metric list. The metric enumeration is long but each item is distinct information an agent needs to judge coverage; nothing is redundant 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 one optional parameter, full schema coverage and annotations covering the safety profile, the main open question is what the tool returns – and the description answers that by listing the metric categories, since no output schema exists. Missing only minor detail on aggregation windows and response shape.

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% and the single optional parameter is fully documented in the schema (pattern, examples, "Omit for the US"). The description only repeats the omit-for-US rule, adding no new syntax or format detail, so 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+resource: an aggregate "roll-up" of nursing homes for a state or the US. The word "roll-up" implicitly distinguishes it from get_nursing_home (single facility) and search_nursing_homes, but it never names those siblings or rank_states_nursing_homes, so the differentiation is left to inference.

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 only usage instruction is "Omit state for the US," which is a parameter rule rather than guidance on when to pick this tool. Nothing tells the agent when to use this roll-up versus rank_states_nursing_homes or get_nursing_home, so the routing is only implied by the word "roll-up."

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