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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful fact that results span policies, promotions, and risk disclosures, but says nothing about result ranking, document scope limits, or freshness.

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 compact sentence with no filler, and the domain scope is front-loaded. It is a fragment rather than a sentence, but it is not padded or redundant.

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 search tool with two undocumented parameters, no output schema, and no usage guidance, the description leaves too much to inference. An agent cannot tell what to pass as the query or how product_ids changes results.

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 0%, so the description carries the full burden for 'query' and 'product_ids' — and it provides none. It never explains what the query string should contain or that product_ids scopes policies to specific products, leaving both parameters semantically undocumented.

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 names the content domain (refunds, cancellation, delivery, merchant of record, risk disclosures, privacy, promotions) so an agent can infer this retrieves storefront policy text, which does distinguish it from search_products. But it never states the action — no verb like 'search' or 'retrieve' — and reads as a topic list appended to a vague 'Storefront:' label rather than a purpose statement.

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?

There is no guidance on when to call this versus siblings such as search_products or get_product_details, and no mention of what kinds of queries are appropriate. The topic list hints at coverage but gives no usage conditions.

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