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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds the counting semantics (residents inside flooded areas) but says nothing about output ordering, tie handling, or defaults; with annotations carrying the safety profile, this is adequate but thin.

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 sentence with no wasted words and the ranking metric stated up front. The parenthetical '(or a year and scenario)' is slightly compressed and could be clearer, but the structure is efficient.

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 six-parameter, no-output-schema tool the description leaves the agent to infer the return shape (ranked list, count) and the mutual exclusivity of rise_m and year/scenario from the schema alone. Nothing is actively wrong, but the description does not fully close the gaps that the missing output schema creates.

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 each of the six parameters is already documented, including the rise_m vs year+scenario alternative and the n/lang defaults. The description merely gestures at the 'sea-level rise (or a year and scenario)' modes without adding syntax or interaction detail beyond the schema, 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?

The description names the resource (planning areas) and the ranking criterion (most residents in flooded areas under a given sea-level rise/year/scenario), which is specific enough to separate it from list_areas and plain area lookups. It is a noun phrase rather than an explicit verb, and it never names the closest siblings (area_impact, flood_impact) to disambiguate.

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?

No when-to-use or when-not-to-use guidance is given, and no alternative is named. This is a real gap because siblings area_impact and flood_impact overlap heavily with a ranked-areas query, and nothing tells the agent which one to pick.

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