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

Annotations already declare readOnlyHint, idempotentHint, and closed-world behavior, so the safety profile is covered. The description adds nothing beyond that — it does not say what the profile contains, whether it is static configuration or live data, or what the caller receives, and the Dutch restatement carries no behavioral information. It does not contradict the annotations.

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?

It is very short and front-loaded, but the second sentence duplicates the first verbatim in another language, which adds length without adding information for most agents. Acceptable if the bilingual pattern is intentional across the server, otherwise waste.

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, no parameters, and no behavioral detail, the description leaves the agent unable to predict what this returns — field names, scope, or whether it includes settings versus descriptive copy. For a no-argument resource fetch this is the main gap and the description does not close it.

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 the baseline is 4 and there is nothing for the description to disambiguate. Schema coverage is nominally 100% with an empty property set.

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 is essentially a noun phrase that restates the title 'Merchant profile' with the brand name appended, and the second sentence is the identical statement in Dutch. It does implicitly separate this resource from siblings like gnv_product and gnv_contact, but there is no verb and no statement of what retrieving the profile actually gives you.

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 guidance on when to call this versus gnv_contact, gnv_product, or gnv_knowledge, and no prerequisites or exclusions are mentioned. An agent must infer that this returns general merchant-level information rather than contact or product data.

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