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

Annotations already cover the safety profile (readOnlyHint=true), so the description's job is to explain the payload, and it does: it discloses the returned dimensions (monthly price per m², new-build vs secondary, renovation, building material) even though no output schema exists. It stops short of stating units/currency, the time coverage, or what happens for an invalid district identifier.

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?

The definition is short and the metric list is front-loaded, but it is telegraphic rather than well-formed prose, and the trailing Russian sentence 'Подробно о районе' is vague filler that restates the tool's purpose without adding information. Removing it would lose nothing.

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 single-parameter read tool with full schema coverage and no output schema, the description covers enough to call it, and the enumerated metrics compensate somewhat for the missing output schema. It leaves gaps an agent would care about: units and currency of the price figures, how many months of history are returned, and behavior on an unknown district.

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 100%: the 'district' parameter is fully documented in the schema, including the English/Russian/Armenian name forms and the numeric 2–13 option with examples. The description adds no additional meaning about the parameter, so the baseline of 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 a specific resource (a single Yerevan district) and enumerates the metrics returned: price per m² by month and splits by new build vs secondary, renovation and building material. That is enough for an agent to distinguish it from market-wide siblings like get_market_overview, though it never explicitly contrasts it with the close siblings get_area_stats or get_street.

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 explicit when-to-use guidance and no named alternative. The phrase 'One Yerevan district' weakly implies per-district granularity as opposed to street- or address-level tools (get_street, estimate_address), but the agent must infer that boundary itself, and the trailing 'Подробно о районе' adds nothing directive.

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