bigcommerce_category

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

The tool clearly states it 'Returns one normalized product-listing page,' which sets output expectations. It does not describe error conditions, rate limits, or what 'normalized' means exactly, but for a read-only GET-like operation this is a reasonable level of transparency.

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?

Two sentences, no filler, each sentence carries meaningful information: what it returns, source domain, and parameter behavior. Concise and precise.

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?

Covers purpose, domain (BigCommerce storefront), and key parameter behavior (url required, page 1-indexed default). Could mention pagination limits or error cases, but overall sufficient for a competent agent 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?

The description notes the `url` parameter must be a 'public BigCommerce storefront category page' and that `page` is 1-indexed with default 1. It does not enumerate all parameters via schema here, but the critical constraints are described. This exceeds the base level of simply naming parameters.

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 states a specific verb and resource: 'Returns one normalized product-listing page from a public BigCommerce storefront category page.' It clearly distinguishes itself from sibling tools like bigcommerce storefront search or other commerce category tools by specifying BigCommerce and 'public storefront category page.'

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 critical usage constraints ('url is required', 'page is 1-indexed and defaults to 1') but does not explicitly state when to use this tool versus other BigCommerce tools, nor when it should not be used. The context is clear enough to infer usage, but no explicit exclusions or alternatives are given.

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