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

Annotations already provide readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds legal scope and time-frame context ('SGB V ab 2015'), but does not disclose output behavior, response shape, or edge cases such as invalid dates.

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 redundant: the German content is repeated in English, and it ends with an incomplete phrase 'dazu Kinderkrankengeld mit 90 …'. It is not tightly structured and contains filler rather than earning every sentence.

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?

As a simple read-only reference tool with fully documented parameters, the description is adequate. However, it does not explain how the optional bestandteil filter affects the result, what the output format is, or how the datum parameter interacts with the stated 'ab 2015' scope.

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 (datum and bestandteil) are already documented in the input schema. The description does not add meaningful parameter-level semantics beyond what the schema provides.

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 clearly states the tool's subject: German statutory sickness benefit (Krankengeld) and child sickness benefit (Kinderkrankengeld), including the relevant legal sections and specific rates/caps/duration. This is specific enough to distinguish it from sibling tools like hr_entgeltfortzahlung or hr_mutterschutz.

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?

No usage guidance is provided beyond the geographic scope 'Nur Deutschland'. The description does not say when to choose this tool over related siblings, nor does it mention exclusions or typical use cases.

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