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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds valuable specifics: it overwrites existing type definitions, the previous value is gone, and there is no history or undo. This directly tells the agent what gets destroyed, beyond the binary flags.

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 purpose and the critical destructive warning are front-loaded, and the description is compact. There is mild redundancy between "kann bestehende Typdefinitionen ueberschreiben" and "Der bisherige Wert ist danach weg (keine Historie, kein Undo)", but overall it is efficient.

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 destructive mutation tool with rich annotations and full schema coverage, the description covers the prerequisite check, the consequence of overwriting, and the undo route. It does not describe any return value, but with no output schema this is a minor gap.

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 both parameters are already documented. The description does not add meaning beyond the schema and even uses the singular "ein Preset" while the schema clarifies that multiple presets are allowed (an array). The baseline of 3 applies because the schema carries the parameter semantics.

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 states a specific verb+resource ("Ein Preset auf einen Scope anwenden") and the effect ("dessen Objekttypen anlegen/aendern"). It distinguishes itself from siblings by naming onto_catalog_index as the prerequisite and onto_catalog_clear as the undo path, though it does not explicitly contrast with onto_catalog_presets.

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?

It gives a clear prerequisite ("Pruefe vorher mit onto_catalog_index, was enthalten ist") and names the undo alternative ("Rueckgaengig: onto_catalog_clear"). It does not state explicit when-not conditions, but the context is sufficient to select this tool.

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