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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description adds genuinely non-obvious behavior: raw narrative text and personal names are deliberately withheld (verify via the url), missing sections come back as unknown rather than omitted, and the output is raw material, not a judgment. It stops short of 5 because error handling for a bad case_id and any size/latency expectations are unstated.

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 with the identity of the tool, then organized into explicit 'facts:' and 'rules:' groupings, with constraints stated last. The long parenthetical field lists are dense but earn their place because there is no output schema. Minor redundancy between the title phrase and the first sentence.

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 correctly does the heavy lifting: it enumerates the returned sections, the 20-record cap on comparables, the unknown-for-missing-section convention, and the explicit exclusion of names and narrative. The only soft spot is that the referenced 'url' is never explained (presumably a returned field), but for a one-parameter read tool this is complete enough to call 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?

There is a single required parameter whose schema description already gives the exact ID format with two examples (100% coverage), so the schema carries the burden. The description adds nothing about case_id semantics, such as where the ID comes from in sibling search results. 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?

The opening sentence names a specific verb+resource: structured material for exactly one court-auction item, mirroring the detail screen. It then enumerates the delivered sections (facts: building/ledger areas, cancellation baseline, tenant facts, fees, comps, other auctions on the same lot, hearing schedule; rules: engine-derived values). It does not explicitly differentiate itself from the sibling get_court_facts, so it stops short of a 5.

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 only implied: singular '1건' plus 'same values as the detail screen' signals this is the per-case lookup reached after a search_court/search_onbid result. There is no explicit when-to-use/when-not and no named alternative, even though get_court_facts is an obvious near-neighbor an agent must choose between.

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