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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's added value is the return behavior: up to 20 lots with price, region, bidding form, application deadline, and link, plus the default sort order. Since there is no output schema, this return-format disclosure is genuinely useful; it stops short of pagination or result-count semantics.

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 sentences, front-loaded with purpose, then return contents, then default behavior. Efficient and well-ordered, though the default-sort statement mildly duplicates what the 'sort' field already documents.

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 read-only search tool with 10 optional params at full schema coverage and no output schema, the description supplies exactly the missing pieces: the domain, the returned fields, and the default ordering. Nothing an agent needs to invoke it correctly is absent.

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%, and every parameter (sort, limit, query, region, channel, category, price, auction_form, property_type) is documented in the schema with enums and defaults. The description adds no parameter meaning beyond what the schema already carries, so the 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 (searches) and resource (lots in the Russian property-auction catalog), and enumerates the auction domains covered (bankruptcy, state, arrested, pledged, commercial). Clear purpose, but it never distinguishes itself from sibling tools like 'search' or 'get_lot', so an agent cannot use the description alone to route between them.

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 description notes a default sort (nearest application deadline) but offers no guidance on when to use this tool versus siblings such as 'search', 'get_lot', or 'market_stats'. No exclusions or preconditions are given; usage is only implied by the domain it describes.

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