bigcommerce_product

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by stating the output is 'normalized product detail' and that it works only on 'public BigCommerce storefront product page' and 'BigCommerce Stencil storefront' – these are informative constraints. However, it does not disclose other behavioral aspects such as error handling, rate limits, or what fields are included in the normalized detail, leaving gaps.

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 concise, consisting of just two sentences. It front-loads the primary purpose and then adds the key URL requirement. There is no redundant or extraneous phrasing; every sentence contributes useful information, making it efficient for an agent to parse.

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?

For a tool with a single parameter and no output schema, the description covers the essential usage information: the purpose, the return type (normalized product detail), and the input format requirement (full public Stencil URL). It does not detail the specific fields returned or potential error conditions, but given the tool's simplicity, it is reasonably complete for an agent to invoke 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 schema already documents the 'url' parameter as 'Full public BigCommerce product page URL'. The description goes beyond this by specifying 'url must be the full public product-page URL for a BigCommerce Stencil storefront', adding the crucial constraint that the storefront must use the Stencil theme. This clarifies the expected input format and platform-specific requirement, adding meaningful semantic value.

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 clearly states the tool fetches a BigCommerce storefront product and specifies that it returns normalized product detail from a public product page. The specific verb 'Get' and resource 'BigCommerce storefront product' distinguish it from sibling tools like bigcommerce_category and bigcommerce_search, which serve different purposes.

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 does not mention when to use this tool versus alternatives. It only states an input constraint ('url must be the full public product-page URL'), but provides no guidance on when to use bigcommerce_product vs bigcommerce_search or bigcommerce_category, which are visible in the sibling list. This leaves the agent to infer appropriate usage without explicit direction.

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