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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so 'Read-only' largely restates structured data. The description does add useful content-level context ('approved' summaries with links to policy pages), but says nothing about return shape, caching, or whether links are absolute.

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, front-loaded with the resource scope. The trailing 'Read-only' sentence is redundant against readOnlyHint in annotations, which costs it a point.

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-parameter, no-output-schema read tool, the description conveys what comes back (summaries plus links to policy pages), which is the key missing piece an agent would otherwise lack. It is complete enough, though a hint about coverage (which policies exist) would help.

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?

Zero parameters, so there is no parameter semantics to clarify; baseline 4 applies. There is nothing the description could add or omit here.

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 resource (shipping and guarantee policy summaries) retrieved in a read-only manner, which is more concrete than the bare name get_policies. It does not explicitly contrast itself with near-neighbors like about_nwb or how_to_use, so it falls short of a 5.

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 by the content type: an agent can infer this is the tool for policy questions, but there is no explicit when-to-use statement and no named alternative for adjacent information needs (about_nwb, how_to_use). Minimum viable guidance.

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