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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), and the description adds substantial context beyond them: the redaction rule for lots no longer open or scheduled (street and postcode district only, no bid figures, no reserve-met flag), error conditions when a lot is not public or auctions are closed, and the fact that personal-interest disclosures and listing text arrive under 'untrusted_user_content' — a meaningful prompt-injection warning.

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 core purpose and then grouped into price, timing, redaction, and trust-boundary clauses; nearly every clause carries decision-relevant information. It is dense and runs long in a single sentence, which slightly hurts scanability but not substance.

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 carries the full burden of telling the agent what comes back, and it does so comprehensively: price fields, fee/deposit obligations, timetable, property, URLs, redacted-lot behavior, and error cases. Nothing essential for correct invocation or result interpretation 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?

There is a single parameter with 100% schema description coverage, so the schema already documents lot_id. The description restates its provenance ('from search_auction_lots') but adds no format, constraint, or edge-case guidance beyond that, 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 and resource ('Full public details of one auction lot by lot_id') and enumerates the content domains returned: prices, bid count, timing, buyer fees, timetable, property, URLs. It also anchors itself to the sibling search_auction_lots as the source of lot_id, so an agent can tell it apart from search and listing tools.

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 clearly implied and partly explicit: lot_id comes 'from search_auction_lots', i.e. call search first, then fetch details for one lot. It also directs the agent to always surface buyer fees and deposit to the user. It stops short of an explicit when-not statement or naming a distinct alternative for bulk retrieval.

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