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

Annotations already declare it read-only, idempotent, and closed-world, so the safety profile is covered. The description adds real value beyond that: it discloses the data provenance, that results carry sample sizes, a 12-month forecast interval, and a public backtest, and critically that it abstains when the sample is too small. Auth, rate limits, and latency are unaddressed.

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 dense sentences with no filler; the data-content summary leads and the abstention caveat closes. Every clause carries information.

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 the return shape, and it does reasonably well (ranges, sample sizes, forecast interval, backtest). It stops short of specifying units/currency or how the forecast interval and backtest should be interpreted, which an agent may need for a data-heavy tool.

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 the area/segment/building parameters are fully documented in the schema, including the list_areas reference and examples. The description adds no parameter-level detail, 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 names the resource (area price/rent snapshot) and its data sources (registered DLD deals, Ejari contracts), which is more specific than the title alone. It does not, however, distinguish this from close siblings like check_price, estimate_rent, or get_market_trend, leaving the agent to infer the boundary.

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?

There is no when-to-use guidance and no mention of alternatives, despite several siblings (check_price, estimate_rent, get_comparables) covering overlapping ground. The only conditional stated is the abstention rule, which is a behavior rather than a selection criterion.

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