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

Annotations already mark it read-only and not open-world, so safety is covered. The description adds valuable behavioral context by enumerating the exact payload returned—prices, reduction stages, deposit, deadlines, organizer contacts, documents—which matters because no output schema exists. It does not mention error/auth/rate-limit 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?

A single front-loaded sentence states purpose and then lists returned fields; no filler. The field enumeration is long but justified by the missing output schema, though it could be mildly structured for faster scanning.

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 tool with annotations and a rich schema, the only real gap would be return details; the description fills that by enumerating the lot card contents. Error behavior is absent but not critical for a simple get-by-id tool.

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 id parameter is fully documented there. The description reinforces the lookup options and adds a concrete URL pattern (torgiopen.ru/lot/…) beyond the schema's generic 'link' wording, giving minor extra meaning.

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 retrieval action on a single lot, specifying lookup by id or torgiopen URL. Enumerates the lot attributes returned (prices, deposit, organizer, documents, source link), which distinguishes it from sibling search/search_lots tools that locate lots rather than fetch a full card.

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 implies usage when an id or lot URL is available, but it never names alternatives such as search_lots for discovery or fetch, nor states exclusions. It provides adequate input context but no explicit when-to-use routing.

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