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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuinely useful behavioral detail — hammer/realized price is only populated 'once sold' — signaling conditional field availability, but it omits any auth, rate-limit, or error context.

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 that names the resource first and then lists the payload fields. No waste, though the field list is dense and reads more like output documentation than purpose.

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 two-parameter read-only lookup with a full output schema and readOnly/openWorld annotations, the definition is nearly complete; the output schema already covers return values. The one gap is the absence of any routing or prerequisite guidance relative to its sibling tools.

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 both parameters (auction_id, lot_number) carry examples in the schema, so the schema does the heavy lifting. The description enumerates return fields rather than adding syntax or format meaning beyond the schema, which is the correct baseline-3 case.

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 names a specific resource (Bonhams lot detail) and enumerates the exact fields returned (title, estimate range, hammer/realized price, sale date, category, department, lot number), so an agent knows precisely what data it yields. It does not, however, distinguish itself from close siblings like bonhams_lot_search or bonhams_auction_detail.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. that you first need an auction_id from bonhams_auction_search), and no routing against siblings such as bonhams_lot_search or bonhams_auction_lots. The agent must infer usage from the name alone.

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