Catalog Search Helper

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds behavioral context: no facet returns available facets, while a facet name returns suggested/valid values that actually exist, which helps the agent understand what the tool will do.

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 with a clear summary, followed by two sentences that explain the two modes and the downstream purpose. Every sentence contributes useful guidance without filler.

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 simple parameter set, full schema documentation, output schema presence, and read-only annotations, the description is complete. It explains when to call, what the two behaviors are, and how the results should be used in catalog_search.

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 extra meaning by explaining that facet values are 'the asset types or review statuses that actually exist' and that results are intended for building catalog_search queries. It does not add detail for limit or query, but those are already well documented in the schema.

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 opens with a specific verb and resource: 'Discover how to search the catalog: list facets, or values for one facet.' It clearly defines two modes and refers to catalog_search, making it easy to distinguish from the sibling catalog tools.

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?

It explicitly explains when to call with no facet versus with a facet, and tells the agent to use the results to build precise catalog_search queries. It does not explicitly state when not to use the tool, but the helper role relative to catalog_search is clear.

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