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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered, but the description adds nothing beyond that — no note on rate limits, pagination behavior, storefront reachability, or how results are ranked. It simply restates the category of operation.

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?

It is short and front-loaded, but it is a bare noun phrase rather than a functional sentence, and the brevity comes from omission rather than from tight writing. Nothing superfluous, but little earned.

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?

An output schema exists, so return values need not be described, but the definition is still incomplete: the required 'url' semantics, pagination, and how results relate to bigcommerce_product remain undocumented. For a 3-parameter, 2-required search tool, this leaves the agent guessing on the key input.

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% for three parameters, and the description does not compensate at all: the highly non-obvious 'url' parameter (a storefront base URL), the query 'q', and the 'page' paging integer are all left unexplained. An agent cannot infer from the text what value 'url' expects.

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) and resource (products) scoped to BigCommerce storefronts, which separates it from bigcommerce_product (single-product detail) and bigcommerce_category in intent. However, it never names or contrasts those siblings explicitly, so differentiation is implied rather than stated.

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 gives no when-to-use guidance: nothing tells the agent when to search versus fetching bigcommerce_product, nor when a different platform search (shopify_search_suggest, shop_app_search) is appropriate. There is also no mention that this targets an arbitrary storefront, which is the key routing decision here.

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