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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds useful domain scope (Israeli places only) and the fact this is the authoritative naming registry, but no rate limits, auth needs, or caveats about data freshness.

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 clauses separated by a semicolon, with the no-argument behavior stated first and the city-argument behavior second. Slightly dense noun stacking, but every phrase carries information and nothing is padded.

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 must convey return values, and it does enumerate them for both branches (coverage list with rent/sale availability and counts; neighborhood registry with ids, slugs, multilingual names, centroids). It is nearly sufficient, though the exact response shape and field names remain unspecified.

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% for the single city parameter, and the schema already explains the name-or-slug form and the omit-for-list behavior. The description restates the same registry contents (ids, slugs, multilingual names, centroids) without adding new semantics, 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 states a specific resource: Dorit's coverage of Israeli cities, regional groups and localities, plus the neighborhood registry returned when a city is supplied. An agent can tell this is a place/name lookup. It does not, however, differentiate itself from the sibling neighborhood_context, which plausibly overlaps with the city-level neighborhood data described here.

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?

"Call this first when unsure how a place is named" gives an explicit trigger condition for invoking the tool, and the schema clarifies the omit-vs-provide branch. No sibling alternative is named for the case where the agent already knows the naming, so it falls short of a 5.

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