bonhams_lot_detail

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

No annotations provided, so description carries full burden. Discloses data source (bonhams.com's own search API), credential-free access, and explicitly states what is NOT returned (full description prose, condition report, additional images). However, does not disclose response format, field types, or error conditions.

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?

Description is efficient and front-loaded with purpose, enumerates key fields, and clearly states omissions in a compact format. No redundant information; every sentence adds value.

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?

Given the tool's moderate complexity and full schema parameter descriptions, the description covers purpose, data source, and exclusions. Does not explicitly guide to how to find auctionId/lotNumber (e.g., via bonhams_auction_lots), but the sibling tools make this inferable. No output schema, but the description lists returned fields, which is adequate.

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 has 100% description coverage, so parameters are already explained ('Bonhams auction id', 'Bonhams lot number'). Description adds no extra semantic detail beyond the schema; omits how to obtain auctionId/lotNumber (e.g., from other tools).

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 ('Get'), resource ('Bonhams lot's normalized facts'), and enumerates the exact fields returned (title, estimate range, hammer/realized price, sale date, category, department, lot number). Distinguishes from sibling tools like bonhams_auction_lots and bonhams_lot_search by focusing on detail retrieval of a single lot.

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?

Implies usage context: to get normalized facts for a specific lot, contrast with search/lot listing. But does not explicitly mention when NOT to use or name alternatives; relies on the tool's purpose to be self-evident among siblings.

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