depop_search_facets

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

Despite having no annotations, the description discloses the key behavioral trait: it is a dedicated aggregates API returning only count breakdowns, not embedded listing data, and the data is public. This prevents an agent from expecting search results or treating it as part of depop_search bulk output.

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?

Every sentence earns its place: initial summary, return details, API source, and public-data qualification. It is three short sentences and front-loaded with the main purpose. No filler or redundancy.

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 single-parameter public tool with no output schema, the description adequately covers what is returned and how via the API. A bit more detail about the shape of the breakdown would help, but given the simplicity of the tool, this is nearly complete.

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?

The schema already fully describes 'query' as 'Free-text keyword search' at 100% coverage. The description adds only 'for a search query,' which repeats the schema without introducing format examples, limitations, or query-construction tips. 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 states a precise verb and resource: 'Returns result-count breakdowns per department/category/subcategory for a search query.' It also distinguishes itself by explaining that it uses a dedicated aggregates API, separate from search responses, which differentiates the tool from siblings like depop_search and depop_search_sellers.

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 clearly implies when to call this tool: when an agent needs aggregate result-count breakdowns rather than search listings. It adds helpful context that this is a distinct upstream call, but it doesn't explicitly name alternatives or exclude when to choose other Depop tools.

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