pristine_marketplace_search

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

With no annotations provided, the description carries the full behavioral burden and does so well. It discloses that the storefront URL is fixed server-side, that the per-page size is fixed at 16 by the theme, and that `limit` only acts as an upper bound rather than a controllable page size. These are non-obvious behaviors that materially affect how an agent invokes the tool.

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 compact and front-loaded: it states the core action first, then the key distinction, then the important constraints. Every sentence earns its place, and there is no redundant repetition of schema details.

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?

The description is largely complete for a search tool with no annotations and no output schema. It covers the source, the distinction from suggestions, the fixed URL, and the limit behavior. A minor gap is that 'normalized products' is not expanded, so the agent does not know the shape of the returned product objects, but this is not critical for selecting or invoking the tool.

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 baseline is 3. The description adds meaningful nuance beyond the schema by specifying the exact fixed page size (16) and clarifying that `limit` is only an upper bound on the returned page. This goes beyond the schema's wording and helps the agent set expectations.

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 this tool searches Pristine Marketplace products and returns normalized results from the storefront's native full-text search page. It explicitly distinguishes itself from the sibling `/pristine-marketplace/search/suggest` endpoint, so an agent can tell them apart without inspecting schemas.

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 explicitly contrasts this tool with the predictive suggestions endpoint, giving a clear when-not-to-use signal. It does not explicitly mention other related siblings like `pristine_marketplace_products`, but the full-text search framing is sufficient for most selection decisions.

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