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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds valuable behavior beyond that: the match is fuzzy (not exact), and each result carries a catalog id, a cited weight in grams, and a verified flag. It stops short of describing pagination behavior or result ordering.

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?

Three tight sentences, zero filler: search scope and examples first, then return shape, then the alternative-tool routing. Every sentence 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 no output schema, the description usefully compensates by naming the returned fields (catalog id, weight in grams, verified flag). Combined with full schema coverage and annotations carrying the safety profile, an agent has everything needed to call it correctly.

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 coverage is 100%, so the schema already documents 'query' (min 2 chars) and 'limit' (1-25, default 12). The description reinforces query intent with examples of brand/product/kind terms, but adds nothing about the limit parameter or result-set sizing. 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?

States a specific verb (fuzzy search) and resource (Mahonia's cited gear catalog), enumerates the searchable fields (brand, product, kind of gear), and gives concrete query examples. It also implicitly distinguishes itself from get_catalog_product by framing this as the discovery entry point.

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?

Explicitly routes the agent to the sibling get_catalog_product with a clear selecting condition ('for every variant of one product'). It doesn't cover the other siblings (add_items, create_list, get_list) or state when not to search, but the key alternative is named.

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