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

Annotations already mark it readOnly and idempotent; the description adds that it covers 'supported' auctions and that fields can be nullable and source-dependent. This is useful but does not disclose pagination, output shape, or source-specific behaviors.

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?

Two sentences with no padding; the core action and a key caveat are front-loaded. Efficient and readable.

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 an 18-parameter search tool with no output schema and only 6% parameter description coverage, this terse description leaves major gaps around filter combination, pagination, and source-specific behavior. An agent would have to infer most semantics from names and enums.

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?

Only one of 18 parameters has a schema description (s), and the description does not compensate by explaining param semantics. The note about exact filters and nullability is generic and not enough to understand the large optional filter surface.

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 it searches supported Copart and IAAI vehicle auction records, with a clear verb and resource. It distinguishes from sibling get/list tools by framing this as a multi-record search, though it does not name any sibling explicitly.

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?

Gives a directive to use exact documented filters and warns fields are nullable/source-dependent, but does not state when to choose this over siblings like get_vehicle or list_auction_locations. No exclusions or alternatives are provided.

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