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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds valuable behavioral context beyond that: it discloses what the response contains and that the original specification and tenant details are reachable via a url, which tells the agent this is a summarized read, not a full document fetch. It does not cover not-found/error behavior, so not a 5.

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?

Front-loaded noun phrase, then a dense enumeration of returned fields, then one short sentence on where deeper detail lives. No filler and no repetition of the title.

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, the description has to describe the return shape, and it does so field by field, which is exactly right for a single-parameter read. A minor gap: nothing about failure modes when the case_id is unknown or when data is missing.

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 single case_id parameter already documents its format with two concrete examples. The description adds nothing about case_id semantics, 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?

States a specific verb+resource (one court-auction item's fact summary) and enumerates the returned facts: price, round, date, expected yield with formula inputs, market comparison, takeover deposit, stake sale. That is far more specific than the title. It does not name a sibling, but '물건 1건' implicitly contrasts with the search_* tools that return multiple items.

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?

The trailing '명세서 원문·임차인 상세는 url로' implies this tool gives summaries and the url gives full detail, which hints at when to use it. However, it never names search_court or search_onbid as alternatives or states prerequisites (e.g., needing a case_id from a search first). Usage is inferred rather than guided.

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