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

Annotations already declare readOnly, idempotent and non-destructive, so the 'Rein lesend' label is partly redundant. However the description adds genuine context beyond the annotations: the cursor is a checkpoint (the state up to which changes were fetched) used in a multi-step workflow, and the 'miss nothing / read nothing twice' guarantee clarifies idempotency semantics.

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?

Front-loads the core meaning and workflow efficiently, but the bilingual duplication plus the trailing keyword tag list ('EN: changes, audit, feed...') adds low-value bulk that dilutes the message slightly.

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 and no parameters, the description carries the load well: it explains what the returned cursor represents and how it fits the change-tracking workflow. It could be marginally richer about whether advancing the cursor happens here or in onto_watch_changes, but it is essentially complete.

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 there is nothing for the description to disambiguate; the baseline is 4. No parameter-level detail is required or missing.

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?

States a specific verb (lesen/read) and resource (Beobachtungs-Zeiger/observation cursor) and defines it ('the point up to which changes have been fetched'). It distinguishes itself from siblings by naming onto_watch_changes for the fetch step and onto_object_index for full-text inventory.

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?

Gives explicit sequencing: read cursor first, then fetch changes, then advance the pointer, and names the alternative for a different need (onto_object_index for the full text inventory). An agent knows exactly when and how to use it relative to alternatives.

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