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

Annotations already declare readOnlyHint=true and idempotentHint=true, and the description adds concrete behavior beyond that: the default limit of 50 messages, oldest-first ordering, and a von_mir flag per message. This enriches the read-only profile with the details an agent needs to interpret results. No contradiction with 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?

Three short sentences each carry distinct information: purpose, source/provenance of chat_id, default behavior and interaction guidance. There is no filler, and the most important fact is front-loaded.

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 simple read-only tool with no output schema, the description gives enough usage context and even reveals a key output field (von_mir). It lacks a fuller description of the returned message fields and any pagination beyond the optional anzahl, which is why it is not a perfect 5.

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 100%, so the baseline is 3. The description restates the default of 50 and the chat_id source, but this adds little beyond the schema, which already documents anzahl as 1-200 with default 50 and chat_id as coming from chats_ansehen.

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 opens with a specific verb and resource: 'Liest den Verlauf einer Unterhaltung' (reads the history of a conversation). It further distinguishes itself from chats_ansehen by stating that the chat_id comes from that tool, making clear that this tool consumes a selected conversation rather than listing conversations.

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?

The description gives explicit timing guidance: 'Nutze das, bevor du antwortest — sonst schreibst du an etwas vorbei, das schon geklaert ist.' This tells the agent to fetch history before replying and why. It does not explicitly contrast with alternatives or state when not to use it, so it stops short of a 5.

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