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

No annotations are provided, so the description carries the full burden. "Public contact path" weakly suggests public accessibility, but it does not say whether the tool reads data, sends a message, returns contact details, requires authentication, or has any side effects.

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?

The definition is short but not efficient: the Dutch translation duplicates the English without adding information, while the substantive content is severely under-specified. The front-loaded phrase is vague rather than useful.

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 one required parameter, no annotations, no output schema, and no parameter descriptions, the definition leaves the agent without enough context to invoke the tool correctly. It does not explain the expected return value or what the agentId controls.

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?

Schema description coverage is 0%, and the description never mentions the required agentId parameter. An agent has no explanation of what an agentId represents or how to obtain the required value.

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 says "Public contact path of the shop," which is essentially a restatement of the tool name with little added precision. It never uses a clear verb such as retrieve, send, or list, and does not distinguish the tool from siblings like gnv_profile or gnv_knowledge.

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 indication of when this tool should be used instead of alternatives, nor any prerequisite or exclusion guidance. The only hint is the word "public," which does not explain the tool's role among the sibling tools.

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