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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered and the description only needs to add context. It usefully discloses that the response is JSON and scopes the policy content, but says nothing about whether these are static values, where they come from, or whether all keys are always present.

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 opens with the resource and format, then packs the policy inventory into a compact parenthetical list. The detail is dense but every clause maps to actual returned content, so it earns its space.

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 no output schema and no parameters, the description carries the job of conveying return values — and it does so by enumerating the policy sections returned as JSON. Minor gaps remain (no statement that the content is static/authoritative or what the contact field contains), but an agent can call it 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 tool takes zero parameters, so per the baseline the schema carries no semantic burden and the description has nothing parameter-related to explain. Nothing is missing 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?

The description states the resource (store policies) and the return format (JSON), then enumerates the exact policy topics covered, so an agent knows precisely what this tool yields. The verb is only implied by the name, and no sibling (create_checkout, quote_order, etc.) shares this domain, so explicit differentiation isn't needed.

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 when-to-use statement, no trigger condition (e.g. 'call when the user asks about shipping, returns, or payment terms'), and no mention of alternatives. Usage is only inferable from the content list, which is weaker than explicit routing guidance.

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