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

The readOnlyHint annotation already establishes this is a safe read, so the description's main added value is the phrase 'wie auf der Website veröffentlicht', which tells the agent the data is a published snapshot that may be stale. It says nothing about return format, size, or whether fields can be missing.

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 sentence that front-loads the returned fields and closes with the publication caveat; nothing is padded. Slightly list-like, but appropriate for a zero-argument profile fetch.

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 parameters and no output schema, the description effectively functions as the return-value contract by enumerating the fields, which is what an agent needs to decide to call it. It could be more complete by noting whether absent fields are omitted or empty and how it differs from get_services.

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 the baseline is 4; there is no argument semantics to explain. The description instead spends its words on output content, which is the right use of space here.

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 specific resource contents returned (name, locations with address and phone, opening hours, services) for 'dieses Betriebs', so an agent knows it is a single-business profile lookup rather than a search. It does not differentiate itself from the sibling get_services, and 'Leistungen' overlaps that sibling's apparent scope, leaving some ambiguity.

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 get_services or the content_* tools; the agent must infer that this returns a business profile and that services may also be obtainable elsewhere. No prerequisites or exclusions are stated.

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