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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior. The description adds concrete detail about what will be returned, including realized price composition, hammer price, estimate range, sale date, and image, which helps the agent set expectations beyond the annotations.

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?

The description is a single front-loaded sentence that names the tool's purpose, then enumerates the returned fields, followed by one short sentence explaining the dependency. Every sentence earns its place with no wasted words.

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 single-lot detail tool, the description covers the input dependency, the scope, and the content of the response. With annotations handling side-effect safety and schema handling parameter semantics, nothing essential 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?

Schema coverage is 100%, so the schema already documents both parameters, including the decorative nature of slug. The description mostly restates the lot_id provenance from phillips_results_search without adding new parameter-level 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?

The description states a specific verb ('Full detail for one Phillips lot') and a clear resource scope, then enumerates the exact fields returned. It is clearly distinguished from the sibling phillips_results_search by targeting a single lot rather than search results.

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 the correct workflow by stating that it takes the lot_id from phillips_results_search, which tells an agent when to use it: after a search has produced a lot id. It does not explicitly list exclusions or contrast with other alternatives, but the dependency is clear enough for correct selection.

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