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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), so the remaining burden is small. The description still adds real value by disclosing the dual-mode behavior (neighborhood present vs. omitted) and the presence of an external browse link, which the annotations do not convey.

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?

Front-loaded with the payload contents, then the fallback mode, then the sibling pointer — a sensible order with no filler. The opening list of return fields is long, but each item is informative rather than padding.

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?

There is no output schema, so the description has to carry the return-shape burden, and it does so thoroughly for both modes. Combined with annotations covering the safety profile, an agent has everything needed to call this 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 description coverage is 100% — city, language, and the neighborhood omit-semantics are all documented in the schema. The description restates the neighborhood-omission behavior but adds no syntax, format, or constraint detail beyond it, 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?

The description enumerates exactly what the tool returns — editorial description, rents by room count, live listing count, rail stations, bordering neighborhoods, and a browse link — and states the fallback mode when no neighborhood is given. It also names a sibling it is not (estimate_price), so an agent can differentiate it without opening schemas.

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?

It explicitly routes priced questions to estimate_price and explains the omit-the-neighborhood mode for city-level data, which is genuine when-to-use guidance. It stops short of clarifying how it relates to the other close siblings (find_neighborhoods_near, search_listings), so it isn't fully exhaustive.

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