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

The readOnlyHint/openWorldHint annotations already cover the safety profile, and the description adds genuinely non-obvious context: the data is not persisted anywhere on the site and only exists at connection time, plus the output language is German. Return shape is covered by the output schema, so nothing major is left undisclosed.

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 core claim ('was beim Verbinden geschehen ist') is front-loaded with concrete sub-items. It is somewhat verbose for a zero-param tool — the sentence about the data only arising at connection time restates the opening premise — and the brief English gloss at the end is the only concession to non-German readers.

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 parameterless, read-only tool with an output schema, the description supplies everything an agent needs: what is returned, why it cannot be obtained from any page tool, and that the response is in German. Nothing relevant to correct invocation is missing.

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. The description correctly describes a call-and-read operation with no input semantics to explain, and there is no misleading implication of configurable input.

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 a specific verb (reports) and a specific resource: what was negotiated during the client-server connection, broken out into MCP version, client name, and client self-registration. The clause 'Diese Angaben stehen nirgends auf der Seite' implicitly separates it from page-oriented siblings like get_page and list_pages, though no sibling is named explicitly.

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 infers it should call this when it wants to know what was negotiated on connect. There is no explicit 'use this when...' statement and no named alternative such as server_info, which is the nearest sibling an agent might confuse it with.

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