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

Annotations already establish read-only, idempotent, non-destructive behavior, so the description only needs to add context. It adds meaningful scope: data is valid only for Germany, federal/uniform, at one Stichtag, and includes specific contribution components. It does not describe edge cases like dates before 2015, but that is beyond the safety profile.

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 compact and front-loaded with key constraints: Germany, federal uniform rates, single date, since 2015. The bilingual repetition of the insurance list is mildly redundant but not bloated. Every sentence carries meaningful scope information.

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 simple one-parameter read-only tool with no output schema, the description conveys the data content (which insurances, employer/employee shares) and the temporal/geographic boundaries. It does not need to explain return values because the description already enumerates the returned items. Missing details like pre-2015 behavior are minor for a Stichtag-based lookup.

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 schema fully documents the optional 'datum' parameter with format and default behavior, so the baseline is 3. The description reinforces the semantic that rates apply at one Stichtag and only from 2015, slightly contextualizing the parameter. No additional format or value details are needed.

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 the exact resource: uniform German social insurance contribution rates (health, pension, unemployment, long-term care) at a single cutoff date from 2015. The 'Nur Deutschland' constraint and the insurance list clearly scope it away from sibling HR tools. It lacks an explicit verb like 'returns/retrieves', but the resource and content are unambiguous.

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 implies usage for querying German statutory contribution rates at a single date, with explicit constraints 'Nur Deutschland' and 'ab 2015'. It provides no exclusions or comparisons to sibling tools such as hr_rechengroessen or hr_mindestlohn that might be confused. The guidance is present but mostly left to inference.

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