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

No annotations are provided, so the description carries the full behavioral burden, and it does not disclose whether data is scraped live from the merchant site, how fresh it is, what happens for unsupported or policy-less domains, or whether calls are rate limited. 'Parse' is also ambiguous about whether the tool fetches the source or only normalizes supplied text.

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?

A single tight sentence with the action front-loaded and the extracted field list acting as useful scoping. The trailing 'for AI shopping agents' is mild audience filler rather than load-bearing content.

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 and no annotations, the description partially compensates by naming the returned data categories, which is genuinely useful. It still omits coverage limits and failure behavior for domains with no published policy, leaving real gaps for a lookup tool.

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 description coverage is 100% for the single merchant_domain parameter and the schema supplies a format example, so the baseline of 3 applies. The description adds nothing about accepted input (bare domain vs URL, subdomains, international storefronts).

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 ('Parse') and resource (merchant return policies), then enumerates the exact fields extracted: return windows, restocking fees, label eligibility, refund methods. An agent can tell this apart from getEcommercePricing or getProductReviewsSentiment by resource, though no sibling is named explicitly.

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?

'For AI shopping agents' identifies an audience but gives no when-to-use, prerequisites, or alternative routing. Nothing tells the agent when to reach for this versus getEcommercePricing or getProductReviewsSentiment in a shopping workflow.

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