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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds useful context beyond them: the storefront must be public, any caller-supplied path/query is ignored, and results are a single normalized page. It doesn't discuss rate limits or auth, but for a public read endpoint that's a minor gap.

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?

Five tight sentences, front-loaded with what the tool returns, then parameter constraints, then the alternative. No filler and every sentence carries 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?

With an output schema present, return values need not be described. Parameters are fully covered by schema plus description, and the sibling alternative is named. Only pagination boundaries (e.g., total pages, result count) are left unstated, a minor omission.

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 baseline is 3. The description adds genuine meaning for url ('optional caller path or query is ignored') and confirms q is required search text and page is 1-indexed/default 1, going slightly beyond the terse schema 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?

States a specific verb and resource ('Returns one normalized product-search page from a public BigCommerce storefront') and explicitly names the sibling it is not ('Use bigcommerce_category to browse...category'). An agent can distinguish it from bigcommerce_category and bigcommerce_product without opening schemas.

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?

Routes the agent to bigcommerce_category for category browsing, giving a clear alternative for the browse case. It doesn't state an explicit when-not condition beyond that (e.g., when to prefer bigcommerce_product for a known item), so it stops just short of full when/when-not coverage.

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