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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context about the calculation basis (Beitragsbemessungsgrenze) and the regional distinction for long-term care insurance (bundesweit vs Sachsen). However, it does not disclose the default date behavior (schema does), the 'at most half' cap when actual contributions are provided, or potential error conditions like dates before 2015, so it only partially enriches the behavioral picture.

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 a single long sentence that mixes German and English, and it trails off with 'und …' and 'contribution …', indicating truncation. It front-loads the 'Nur Deutschland' constraint but then packs the calculation logic into a run-on structure. It is not an egregiously long description, but the bilingual duplication and incompleteness hurt readability and structure.

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?

There is no output schema, so the description carries the full burden of explaining what the tool returns. It mentions the maximum subsidy amount but does not mention the output field names (zuschuss_kv_monat, zuschuss_pv_monat) or how the response changes when optional contributions are provided. It also omits important operational details such as the date range validity (ab 2015) and what happens for earlier dates. These are significant gaps for a calculation tool with no structured output definition.

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 each parameter is already documented with meaning and effect. The description adds only marginal context by framing the parameters as 'Monatsbeitrag' and 'Stichtag', but it mostly repeats or implies what the schema states. It does not explain how the optional contributions interact with the maximum, such as the half-contribution cap, which is already in the schema descriptions. Therefore, a baseline 3 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 states a specific verb ('berechnet' / 'calculated') and a clear resource: the maximum monthly employer subsidy for private health and long-term care insurance since 2015. It names the calculation basis (contribution assessment ceiling) and the two insurance types, which distinguishes it from sibling tools like hr_beitragssaetze or hr_bav_hoechstbetraege. However, the description is truncated ('und …') and mixes German and English, which slightly reduces clarity about the exact computation.

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 only usage guidance is the constraint 'Nur Deutschland' and 'ab 2015'. It does not explain when to use this tool versus alternatives, when to provide the optional contribution parameters, or what the returned values mean in different scenarios. There is no mention of exclusions or prerequisites beyond the date and location, leaving the agent without clear decision criteria.

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