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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the scope of what is returned but does not disclose additional behavioral traits such as ordering, caching, or response size. With annotations present, this is adequate but not rich.

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 description is one focused sentence, front-loaded with the action ('Liefert eine Übersicht') and followed by the precise objects covered. No filler or redundancy.

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 parameterless, read-only options-retrieval tool with an output schema, the description is complete. It tells the agent exactly what domain data is covered, while the output schema covers return structure and annotations cover safety.

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 has zero parameters and 100% schema coverage, so there is nothing for the description to compensate for. According to the baseline for no-parameter tools, a 4 is appropriate.

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 uses a specific verb ('Liefert eine Übersicht') and names the exact resource: all Dienstherren (Bund & 16 Bundesländer), collective agreements (TVöD, TV-L, etc.), and available Besoldungsgruppen. This clearly distinguishes it from the calculator siblings, which focus on salary computation rather than option listing.

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 clear context: this tool returns an overview of public-sector employers, tariff agreements, and salary groups. It does not explicitly name exclusions or alternatives, but the content makes its role as an options/metadata lookup self-evident compared to the calculate_* siblings.

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