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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description's main added value is disclosing the return payload's contents, which matters since there is no output schema. It says nothing about behavior when a region is ambiguous or not found, or about default granularity when only `region` is supplied.

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 content is front-loaded with the reportable metrics, which is good. However, the English and Korean sentences are near-verbatim duplicates of the same information, so roughly half the text is redundant for a bilingual-reading agent.

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, enumerating returned metrics is genuinely necessary and done. But the tool has zero required parameters, and the description never says whether `region` or `bjd_code` alone suffices, what happens if both are omitted, or what resolution order applies — a meaningful gap for a two-optional-parameter lookup 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 coverage is 100% and the schema descriptions are strong — `region` gives concrete format examples and `bjd_code` explains that it comes from a prior result's bjd_code for drilling into sub-regions. The description reinforces the drill-down path by naming sub-regions ranked by price, adding mild context beyond the schema. Nothing new about parameter syntax, but the baseline for full coverage is 3 and the sub-region linkage gives a small lift.

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 resource (province/district/neighborhood apartment market data) and enumerates the metrics returned — price per pyeong, rank, change rates, jeonse ratio, transactions, listings, sub-region ranking. That is far more concrete than a tautology. It does not, however, distinguish itself from siblings like get_apartment_overview, get_recent_trades, or get_price_history, which appear to overlap with subsets of this data.

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?

Usage is implied by the region granularity (시도·시군구·읍면동) and by the mention of sub-regions ranked by price, which hints at drill-down exploration. But there is no explicit 'use this when…' statement and no guidance on when to prefer get_recent_trades or get_price_history over this aggregated view.

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