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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so 'Read-only' in the description merely repeats structured data and earns no credit. The description does add a return-format hint that results include links to policy pages, which is useful context, but it says nothing about freshness, caching, or failure modes.

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?

Two short sentences with no filler; what the tool returns is front-loaded, and the read-only note is brief. Nothing could be cut without losing information.

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 no-argument, read-only retrieval tool with no output schema and full annotation coverage, the description tells the agent what content to expect and that links are included. It could add a note on when content might be missing or stale, but it is sufficient to call the tool correctly.

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?

The input schema has zero parameters, so the baseline is 4. Nothing in the description misrepresents or omits parameter behavior since there is nothing to parameterize.

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 (approved shipping and guarantee summaries, store policy pages) with a clear scope, letting an agent distinguish it from siblings like about_nwb or how_to_use. It is not a tautology of the name, though it lacks an explicit verb such as 'retrieve'.

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?

The purpose implies when the tool is relevant (questions about shipping or guarantees), but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives. For a zero-parameter, single-purpose lookup tool the intent is largely self-evident, so this is adequate rather than strong.

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