slickdeals_search_advanced

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

No annotations are provided, so the description carries the behavioral burden. It discloses a notable behavior: facet values and counts are scoped to the current query, not site-wide, and `sort` is passed through unvalidated. It does not, however, disclose pagination limits, rate limits, authentication requirements, or what happens on empty results. For a read-only search tool the safety profile is fairly obvious, and the description does add nontrivial behavioral context, but it stops short of being fully transparent about response behavior.

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 long but information-dense, and every sentence earns its place: it contrasts with the sibling, enumerates return-value enhancements, clarifies facet scoping, and explains sort behavior. It is front-loaded with the key purpose and the sibling contrast. It could be tightened slightly — the facet explanation is somewhat repetitive — but the verbosity is justified by genuinely useful detail.

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?

Given the tool's complexity — 6 parameters, facets, pagination, and a contrasting sibling — the description is quite complete. It covers purpose, sibling differentiation, facet semantics, sort behavior, and return-value highlights (pagination fields, counts, fuller per-deal records). There is no output schema, so the description's mention of return fields is helpful. It lacks explicit pagination limits or error/empty-result behavior, but for a search tool with a rich input schema, the coverage is strong.

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%, so the baseline is 3. The description adds real value beyond the schema by explaining that `category_id`/`brand_id`/`store_id` are passthrough filters that must be sourced from a prior response's facets and are not validated against a closed enum. It also clarifies that `sort` is unvalidated and defaults to relevance. This is meaningful semantic guidance beyond the property descriptions.

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 and resource: "Search Slickdeals with real pagination, counts, and facets." It clearly differentiates from the sibling tool `slickdeals_search` by contrasting against "GET /slickdeals/search's keyword-only RSS feed" and calling this "a richer alternative." An agent can distinguish the two without opening 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 positions this tool as the richer alternative to the keyword-only `slickdeals_search`, giving an agent a clear when-to-use signal. It also explains when to use facet values: they come from a prior response's own facets and are passthrough filters, not validated enums. It further guides on sort behavior (defaults to relevance, others passed through unvalidated), leaving little ambiguity about usage.

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