pristine_auction_search

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

No annotations provided, so the description carries the full burden. It discloses that it's credential-free public data, which is a useful behavioral trait. It also explains the default behavior (all statuses) and that the search mirrors the site's own default. However, it doesn't specify what the response contains or any rate limits, but the credential-free note adds valuable 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?

The description is reasonably concise, with key constraints front-loaded (term or category required). Each sentence adds value: what it does, source limits, enum origin, special status behavior, filter combination, and credential-free note. It's structured logically and doesn't waste space.

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 search tool with 9 parameters and no output schema, the description covers the essentials: what it searches, required inputs, filter semantics, and the special status behavior. It doesn't describe pagination or output structure, but since no output schema exists, this might be a gap. However, the description is robust enough for an agent to invoke correctly.

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 every parameter is described in the schema. The description adds a bit: it clarifies that term or category is required, that status=completed is a special case, and that filters combine with AND. It doesn't elaborate on each parameter beyond schema, but given high coverage, baseline 3 is appropriate.

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 clearly states it searches Pristine Auction's live auction inventory, specifically sports cards and memorabilia lots. It mentions browsing or searching, matching the site's own search form. It distinguishes itself by noting the required term or category and references the sibling pristine_auction_categories, differentiating it from other 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?

Explicitly states that term or category is required, and that all filters are optional with AND semantics. It describes when status=completed should be used (browsing ended/sold lots) and when to omit it (all statuses). It also mentions that enum values come from pristine-auction-categories, guiding the agent to fetch valid values from sibling tool.

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