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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description is free to add substantive data-quality behavior: a 30+ transaction threshold and a default residential-only class filter that excludes whole-building leases and land deals. It goes beyond annotations meaningfully, though it never says what the result set looks like.

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 tight sentences, front-loaded with the ranking statement and followed by the caveats that change the numbers. Zero filler for the amount of information conveyed.

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?

No output schema exists, so the description ideally would say roughly what a ranked row contains (community name plus median value); it doesn't. Otherwise the caveats and metric semantics are sufficient to call the tool correctly.

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 50% — metric and propertyClass are documented in schema, while order and limit are not. The description compensates partly by explaining the effect of omitting propertyClass and naming the two metric forms, but it says nothing about the limit parameter or its 3–15 bounds. Adequate, not complete.

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 (ranks) and resource (communities) plus the two ranking metrics, and disambiguates from rank_buildings by naming the geography being ranked. An agent can tell exactly what question this tool answers.

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?

Gives concrete user phrasings the tool serves ('cheapest areas', 'most affordable rents'), which is strong positive routing guidance. It does not explicitly state when to prefer rank_buildings or get_location_stats instead, but the community scope makes the boundary reasonably clear.

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