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

Annotations already establish that this is a read-only, closed-world lookup, so the safety profile is covered. The description adds genuinely useful behavior — the query string itself carries region, price, property type, and auction type — but says nothing about result ordering, matching semantics (keyword vs semantic), limits, or pagination.

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?

Two sentences, front-loaded with the resource and immediately followed by illustrative examples; no filler. Slightly denser than needed for a single-parameter tool, but every element is useful.

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?

For a one-parameter read-only search this is close to adequate, but with no output schema the description should have said what comes back (list of lots, fields, ordering). It also leaves the search_lots overlap unresolved, which matters for correct tool selection.

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 schema itself says only «Фраза поиска», so the description earns credit for explaining that region, price, property type, and auction type are encoded inside the phrase. That is meaningful construction guidance beyond the schema, though it does not cover syntax details or how conflicting tokens are resolved.

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 gives a specific verb and resource (поиск лотов торгов имуществом в России) and clarifies the input modality as a free-form phrase, with three concrete examples. It is clear what the tool does, but it never distinguishes itself from the sibling search_lots, which reads like an overlapping search tool, so an agent cannot tell them apart from the text alone.

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: the examples show the kind of free phrase to pass, but there is no statement of when to prefer this over search_lots, fetch, get_lot, or market_stats, and no exclusions or prerequisites. Given a near-duplicate sibling name, the absence of routing guidance is a real gap.

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