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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds value by framing the data as a 'Public overview' and by enumerating the exact content scope (schedule history, appraisal notes, rights summary), which tells the agent what will come back without calling the tool. It does not mention pagination or gaps, but neither applies to a single-item read.

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 front-loaded correctly, and the English field list earns its place, because there is no output schema. However, the Korean sentence repeats the English content almost verbatim, which pads the definition without adding information for an agent that already reads the English. Removing that duplication would make it tighter.

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?

Because there is no output schema, the description is responsible for explaining the return shape, and it does so comprehensively by naming the case number, court, prices, failed rounds, bidding date, history, appraisal notes and rights summary. Combined with annotations covering the safety profile, an agent has enough to call it correctly. Usage routing to search_auctions is the only missing piece.

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?

There is only one parameter and schema description coverage is 100%, so the schema fully explains auction_id, including its format example (C88PQDUZ) and source. The description adds no parameter-level meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 statement of what the tool does: 'Public overview of one court auction item,' and then lists every field it returns, so an agent can tell it apart from list-oriented siblings such as search_auctions. Is it explicitly stated that this tool returns a single item rather than a set, but it does not name the sibling it complements or say how it relates to search_auctions.

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 sentence explaining when to use this tool versus search_auctions or get_auction_stats. The only pointer to an alternative is in the auction_id schema text ('search_auctions 로 얻은'), and that is structured data, not description guidance. The usage pattern (fetch an ID, then get the details) is implied rather than stated.

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