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

Annotations already declare readOnly, openWorld, non-idempotent, non-destructive, but the description adds substantial context beyond them: pay-per-call billing in stablecoins, a no-charge guarantee for non-Shopify sites or empty stores, and a refund promise for unpaid results. It also enumerates the returned fields, which is valuable given no output schema exists.

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?

Front-loaded with the core action and scoping bound, then the return fields, then billing terms. The opening phrase 'for AI agents' is mild filler and the return-field list makes the first sentence dense, but the structure is otherwise efficient with no wasted sentences.

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 no output schema, the description compensates by listing returned fields, and it covers billing and failure semantics. What is missing is any guidance on response shape, pagination beyond the 250 cap, or ordering, but for a two-parameter read tool this is nearly complete.

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%, and the schema itself documents the limit capping/clamping behavior and the accepted domain formats in detail. The description only restates 'up to 250' and 'send a store's domain', so it adds little beyond the structured fields — baseline 3 is appropriate.

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 ('send a store's domain and get up to 250 of its public products'), and the Shopify scoping clearly separates it from siblings like amazon, ebay-sold, or web-search. An agent can identify exactly what it returns without opening the schema.

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 context is implied by the title and the required 'store' domain parameter, but there is no explicit when-to-use versus when-not, nor any routing to an alternative sibling when a site is not a Shopify store. Adequate but leaves the agent to infer that this is the Shopify-specific choice among marketplace tools.

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