catalog_search_helper

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

With no annotations provided, the description carries the burden. It explains the two operational modes and that the tool helps build queries. It does not disclose behavioral traits like destructive actions or authentication needs, but the tool appears to be a read-only helper, and the description adequately conveys its functional behavior without contradictions.

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 three sentences, well-structured with clear instructions. It front-loads the purpose and then provides specific usage details. No extraneous information.

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 that an output schema exists (mentioned in context signals), the description does not need to explain return values. It covers the two modes, parameter usage, and the relationship with catalog_search, making it complete for this 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 100%, but the description adds significant value by explaining the dual-mode behavior of the 'facet' parameter (null vs string) and how the 'query' parameter filters differently based on mode. This goes beyond the schema's individual parameter 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 clearly states the tool's purpose: to discover how to search the catalog, list facets, or values for one facet. It distinguishes two modes (with and without 'facet') and explains how the results feed into catalog_search. This is specific and differentiates it from sibling tools like catalog_search.

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 says when to call with no facet (list available facets) and when with a facet (get suggested values). It also advises using results for building catalog_search queries. However, it does not explicitly mention when not to use it or alternatives, but the context is clear.

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