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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the useful detail of which policy topics are present, but says nothing about the shape of the response (structured policy sections vs. free text) or whether it is a static snapshot that may be stale. With annotations carrying the safety burden, a 3 is appropriate.

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 compact sentence that front-loads the resource and then lists the covered topics in a scannable order. Every clause maps to actual retrievable content; nothing is redundant.

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 zero-param, read-only information tool with no output schema, the topic enumeration is the main thing an agent needs to decide to call it. The only residual gap is not knowing the return format (plain FAQ text vs. sections), which is minor given the tool's simplicity.

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, which is the baseline-4 case. The description implies no input is needed, consistent with the empty schema, and there is nothing further an agent needs to supply.

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 the resource (store policies) and enumerates the covered topics: delivery area/time/fee, cash-on-delivery, order confirmation, returns, and support contact. This clearly distinguishes it from the siblings (get_order_status, get_product, place_order, search_products), which are transactional. It stops short of a verb like 'returns' or 'retrieves', so an agent must infer that calling it yields policy text, but the content scope is specific enough to act on.

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 should call this for delivery/payment/returns questions – but the description never states when to use it versus siblings, nor any exclusions. With a zero-parameter FAQ tool the routing is fairly self-evident, so implicit guidance is acceptable but not exemplary.

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