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

Annotations already declare this a safe, read-only, idempotent, non-open-world content lookup, so the burden is light. The description adds real value by disclosing exactly what the guide covers (insured pack request, XRF testing on camera, itemised offer, bank transfer, free returns, ID requirements, return postage rule), letting the agent predict the answer scope.

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 sentence, front-loaded with the core purpose, then a compact colon-delimited coverage list. Every clause earns its place, though the enumeration is dense and could be trimmed slightly.

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?

No params and no output schema, so the description only needs to convey what knowledge it returns, which it does thoroughly. The remaining gap is sibling differentiation against how_to_sell, which is a routing concern rather than a completeness one.

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 no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The listed topic headings serve as implicit content selectors even though no input exists.

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 topic with a clear verb-ish framing ('The postal selling process step by step') and enumerates the covered subject matter. It is clear what the tool returns, but it never distinguishes itself from the very similar sibling how_to_sell, so the agent must guess between the two.

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 that needs to explain the postal selling journey would pick it, but there is no explicit when-to-use statement, no exclusion, and no routing to how_to_sell, get_guides, or get_faq which overlap in content.

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