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

With no annotations, the description carries the full burden, and it delivers: it discloses that the verdict is the graded band of the same score (with thresholds), that mid scores are neutral by design, that price is volume-weighted from MOLIT transactions, that the call is informational, and that a 402 challenge must be retried with a PAYMENT-SIGNATURE header. It also reveals the per-timeframe breakdown returned behind the score.

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 description is dense but front-loaded: the first sentence states the core action, followed by grading, data source, payment, and sibling comparison. Most sentences earn their place given the absence of annotations and output schema, though the payment and marketing details could be trimmed without losing key calling instructions.

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?

Despite having no output schema, it explains the return structure (daily/weekly/monthly verdict and vote counts behind the score), the exact grading thresholds, the price definition, the payment flow, and input format. For a single-parameter tool, nothing essential is missing for an agent to select and invoke it 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?

The input schema already documents symbol with examples, so baseline is 3, but the description adds important meaning by specifying accepted forms: Korean (강남구, 강남) or romanized (Gangnam, Nowon, Mapo) names. It clarifies the symbol corresponds to one of the 25 covered districts.

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 opens with a specific verb and resource: 'Return the bottom/top verdict for one Seoul district apartment market (25 districts).' It also distinguishes the tool from its sibling by noting that 'this tool answers ANY symbol in the covered universe' while pitch covers 'this market's showcase symbol only.' The grading semantics (strong_buy/buy/neutral/sell/strong_sell and -100..+100) make the purpose unambiguous.

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 provides clear usage context: pass a district in Korean or romanized form, and use this tool instead of the free pitch tool when you need any symbol rather than the showcase one. It does not explicitly mention scan_bottoms/scan_tops or the other siblings, so the when-not-to-use guidance is not fully complete.

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