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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so 'Rein lesend' mostly repeats structured data. The description adds useful workflow context (preview before apply) but says nothing about output shape or size, which is the main remaining behavioral unknown.

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 purpose and the pre-apply guidance are front-loaded in one compact sentence. The trailing EN keyword list ('catalog, preset, template, apply, clear') is slightly noisy and mixes in sibling concepts like apply/clear, but it does not obscure the main instruction.

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 zero-parameter, read-only catalog listing, the description covers what the tool returns conceptually (which types are in which presets), how it relates to apply/clear/presets siblings, and when to use it. Missing only explicit return-shape detail, which is not critical here.

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 parameter semantics are trivially satisfied. The description does not need to explain any arguments.

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 gives a specific verb and resource: reading the object-type catalog (which types are bundled in which presets). It also explicitly contrasts with the sibling that lists presets (onto_catalog_presets), so an agent can distinguish them without inspecting schemas.

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 states a concrete use case: check what a preset contains BEFORE applying it, and points to onto_catalog_presets for listing available presets. It lacks explicit when-not-to-use guidance, but the pre-apply workflow is clear.

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