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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds one genuinely useful behavioral fact: the window is fixed at 12 months and aggregation is done both monthly and by property type, which tells the agent no custom date range is possible. No rate limits, response size, or error behavior are mentioned.

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 metric list is front-loaded and useful, but the English and Korean sentences are near-verbatim duplicates of each other, roughly doubling length without adding information. The content is otherwise tight with no wasted filler.

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?

There is no output schema, so the description carries the burden of explaining return shape, and it does: counts, sale ratio, and price ratio, sliced monthly and by property type. An agent knows what it will get; only the nationwide default behavior and relative sizing of results are left implicit.

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%, and the schema itself documents sd ('비우면 전국') and sgg ('sd 와 함께'). The description only restates 'province/district' and adds no format or interaction detail beyond the schema, so 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?

It gives a specific verb+resource ('Court auction statistics') and enumerates the exact metrics returned: auction counts, sale counts, sale ratio, and winning-bid-to-appraisal ratio, broken down monthly and by property type. That clearly distinguishes it from search_auctions and get_auction, though those siblings are never named explicitly.

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?

Use is implied by the fixed 'last 12 months' window and the region scoping, and the Korean text adds that an empty sd means nationwide (which duplicates the schema). There is no explicit statement of when to choose this over search_auctions or get_region_market, and no exclusions.

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