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

Annotations already declare readOnlyHint and openWorldHint, so the description's added value is the response-shape disclosure (normalized fields including buy_url, ships_to, source) and two real obligations: surfacing the `disclosure` text to users and not caching results. It stops short of stating rate limits, result-count behavior, or what happens when nothing matches.

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?

Three short sentences, front-loaded with the capability, then result shape, then the two operational rules. Every sentence carries non-redundant information and nothing is padding.

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 well by enumerating the returned fields, and it flags the mandatory disclosure obligation. For a five-parameter open-world search it is nearly complete, though it omits empty-result behavior and any cap/pagination note (the limit maximum of 20 lives only in the schema).

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 80% and every parameter carries a description with format/pattern rules, so the baseline of 3 applies. The description adds nothing parameter-specific — the currency and ships_to mentions appear in the list of returned fields rather than as query constraints, so it does not deepen understanding beyond the schema.

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 ('Search') plus the resource ('live products') and names both underlying sources (Shopify Global Catalog, Channel3), so an agent knows exactly what corpus is being queried. No siblings exist to disambiguate against, and the source enumeration does the disambiguation work on its own.

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 only implied: the tool searches live commerce data, and the description adds operational mandates ('always show disclosure', 'do not cache'). There is no explicit when-to-use or when-not-to-use guidance, no statement about typical query patterns, and no alternatives are named.

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