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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so the safety profile is covered. The description adds useful framing that this is verbatim authoritative text ('the store's own wording') and that shipping applies to the US only, but says nothing about response shape or how topics are combined.

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 front-loaded sentence that identifies the resource, the source of truth, and the covered topics with zero filler. The parenthetical '(US only)' earns its place as a constraint.

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?

This is a simple read-only lookup with one optional enum parameter, full annotations, and an output schema, so the description need not explain returns or pagination. Nothing an agent needs in order to select and invoke it correctly is missing.

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 single enum parameter is fully documented, including the 'default all' behavior, so the description need not repeat it. The enumerated topics in the description loosely mirror the enum but add no new syntax or constraint information.

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 a specific resource (store policies) and enumerates the exact subject areas covered: shipping, payments, returns, minimums, pickup, and selling. It distinguishes itself from price/product siblings by being clearly policy text, though it does not explicitly contrast with get_store_info, which is the nearest neighbor.

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 the topic list — an agent can infer this is the tool for policy questions — but there is no explicit 'when to use this instead of get_store_info' guidance or statement of when not to call it. The default-all behavior is left to the schema.

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