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

With no annotations, the description carries the full burden and discloses meaningful behavior: it searches KlickyMart-observed offers and optionally the live Shopify Catalog (never stored), returns specific fields including conditional est_total, and explains unindexed stores. It stops short of stating auth needs, rate limits, or explicit read-only safety.

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 front-loaded with the core action ('One call: a product's landed price at a US ZIP') and every clause adds useful detail about sources, returns, or edge cases. It is dense and long but not wasteful; light restructuring could improve scanability.

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?

The description thoroughly explains return values and source behavior, which is important because there is no output schema. However, for a 14-parameter tool with low schema coverage, it leaves too many input parameters undocumented and offers no sibling-tool routing guidance.

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?

There are 14 parameters with only 29% schema description coverage. The description adds meaning for zip and live, but leaves most parameters—q, mpn, url, gtin, type, limit, domain, in_stock, condition, max_price, max_landed, brand_strict—unexplained, so it does not compensate for the low schema coverage.

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: fetching a product's landed price at a US ZIP by searching offers and optionally the live Shopify Catalog. It is clear what the tool does, but it does not explicitly distinguish itself from sibling tools like find_offers or get_checkout_map.

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?

Usage is implied by 'a product's landed price at a US ZIP' and the live=true behavior, but the description gives no explicit when-to-use vs when-not guidance and does not name alternatives such as find_offers. An agent must infer the selection criteria.

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