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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds genuine context beyond that: it discloses pagination behavior, that counts come back as integers, and that category_id/brand_id/store_id are passthrough filters sourced from a prior response's own facets rather than a validated enum. Return values are handled by the output schema.

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, zero filler, front-loaded with the capability summary followed by the differentiation and the facet caveat. Every clause earns its place.

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?

With an output schema handling return shape and annotations covering the safety profile, the description only needs to add selection and filter context. It covers the differentiators and the facet-derived id filters well but leaves page/sort/q semantics unaddressed for a six-parameter search 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 description coverage is 0%, so the description must carry the load, and it does only partially: it clarifies the origin and nature of category_id/brand_id/store_id (facet-sourced passthrough, not a closed enum). It says nothing about q, page, or sort semantics. Baseline 3 reflects meaningful but incomplete compensation for three undocumented parameters.

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 a specific verb (Search) plus resource (Slickdeals) and enumerates the concrete differentiators: real pagination, integer vote/comment/view counts, and id+count facets. It explicitly separates itself from the sibling slickdeals_search ('richer alternative to slickdeals_search's keyword-only RSS feed'), so an agent can route without opening either schema.

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?

Names the alternative tool and the axis that distinguishes them (richness vs keyword-only RSS), which routes the agent toward this tool for advanced querying. It lacks an explicit 'when not to use' or a rule for the q-only simple case, but the comparative framing is clear.

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