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

Annotations already carry the full safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is low. The description adds only the word "published", signaling these are authoritative public documents rather than drafts or user-generated content — useful but thin, and it says nothing about whether results are cached, versioned, or dated.

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?

One front-loaded sentence with no filler; every listed item corresponds to real retrievable 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 one optional parameter, no required inputs, and rich annotations, the call mechanics are well covered. However, there is no output schema, so the description should indicate what a policy read returns (full text, structured sections, links) — that gap is unaddressed.

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 0% and the single parameter is an undocumented enum, but the description does list policy domains that map onto the enum values (returns, shipping, style_pass, privacy, terms, protection), effectively naming them. It never states that the parameter selects among these, that "all" is the default, or that "exchanges" is folded into returns rather than being its own enum value.

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?

Specific verb ("Read") plus a precisely scoped resource ("FRW's published returns, exchanges, shipping, Style Pass, privacy, terms and package protection policies"). The enumerated policy domains leave no ambiguity about what comes back, and no sibling tool (catalog/product/review tools) overlaps with this read.

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 only implied: an agent can infer this is the tool for customer questions about returns, shipping, privacy, etc. There is no explicit when-to-use framing, no prerequisites, and no mention of alternatives or exclusions.

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