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

No annotations exist, so the description carries the full burden. It does disclose the shape of the returned data (per-country status buckets, outdated counts, oldest check date, last sync), which implies a read-only inspection. However, it never states explicitly that the call is read-only, whether results are cached or how fresh they are, or any permission requirements.

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?

Two compact clauses: first the returned content, then the intended use. It is front-loaded with the payload and contains no filler or repetition, though the first clause is dense with colon-separated sub-items.

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 annotations, no output schema, and no parameters, the description is the only source of information, and it does describe the returned fields reasonably well. It stops short of defining what belegt versus zu_pruefen mean operationally or how the caller should act on outdated entries.

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 for a parameterless tool applies. The description adds no parameter-level meaning, which is appropriate here.

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 resource (the catalog state) and enumerates the concrete information returned: per-country belegt/zu_pruefen, count of outdated entries, oldest check date, and last automatic source reconciliation. That is far more specific than a restated title, but it never contrasts itself with the enumerated siblings (angebot, pflichten, vat_pruefen, etc.), so differentiation is only implicit.

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 one usage condition: check catalog quality before using or recommending DutyKit. There is no guidance on when not to call it, no prerequisites, and no alternative tool named, so the when-to-use signal is present but thin and framed around DutyKit rather than tool selection.

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