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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered and the only added signal is "public" (implying no auth). With no output schema, the description carries the burden of saying what comes back, and it says nothing — one cannot tell whether the result is a string, a link, or a structured contact block.

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?

Very short and front-loaded, but roughly half the text is a Dutch restatement of the same sentence, which adds no decision-relevant information for an agent. The saved space could have carried a return-value hint.

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 lookup with no output schema, the description should at least characterize the returned content (contact details vs. a page link). It leaves that entirely unspecified, so an agent cannot judge whether calling it satisfies a contact-information need.

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 there is nothing for the description to disambiguate; baseline 4 applies. No partial or misleading parameter claims are made.

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?

"Public contact path of the shop" names a resource (shop contact) and a qualifier (public), which distinguishes it reasonably from the catalog/product/knowledge siblings. However, "contact path" is ambiguous about what the tool actually returns — a URL, an address, phone/email fields, a web form? The verb is missing entirely.

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?

No guidance on when to invoke this versus the other shop tools, and no prerequisites or exclusions stated. An agent must infer that contact requests belong here purely from the word "contact".

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