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

Annotations already declare readOnly/idempotent/non-destructive, so the description correctly spends its budget on non-obvious behavior: only the top 3 results carry computed values (예상 수익률, 시세 대비, 인수 여부) while the rest are null, and the output is factual rather than a recommendation. That null-truncation rule is a genuinely load-bearing disclosure an agent would otherwise misread as missing data.

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?

Three dense sentences with the verb+resource front-loaded, then output shape, then the caveat about non-recommendation. Every sentence carries information; the phrasing is terse but not padded.

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 10 parameters, no output schema, and no required fields, the description does the necessary work of describing the return shape (per-item fields, null behavior for ranks 4+, detail URL as escape hatch). The only omission is that result-set size capping (limit ≤ 10, no pagination) is left entirely to the schema rather than flagged as a truncation caveat.

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 every one of the 10 parameters is already documented, including enums and the limit maximum. The description adds no parameter-level semantics beyond what the schema states, which is the expected baseline-3 outcome here.

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 verb+resource: searching in-progress court-auction listings on 파공넷, and enumerates the fields returned (사건·소재지·최저가·매각기일·유찰 횟수·상세 URL). It is clearly distinguishable from get_court_facts and search_bankruptcy, though search_onbid is never explicitly contrasted, so sibling differentiation is only implicit.

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 resource ('법원경매 진행 물건 검색'), but there is no explicit when-to-use/when-not guidance and no routing to search_onbid or get_court_facts for detail lookups. The only forward reference is '“url에서 확인”', which is a data-access hint rather than a tool-selection rule.

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