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

Annotations indicate readOnlyHint=true, idempotentHint=true, and no destructive action. The description adds context about using the BMF's Programmablaufplan and supports precise tax/social insurance calculations, which is useful. However, it does not disclose important behaviors like requiring specific inputs for certain employment types, potential errors for invalid combinations, or that 'sonstige' requires bruttoGehalt, though the schema does indicate that. No contradiction found.

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 two sentences, but it is dense with technical jargon and German acronyms, which may hinder quick comprehension. It front-loads the main purpose but is not as concise as it could be, given the complexity of the tool. It is not overly long, but it could be restructured for clarity.

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?

Given the tool's high complexity (27 params, 9 enums, multiple employment types), the description covers the core modes and mentions exact tax/social insurance calculations, but it omits guidance on how parameters interact (e.g., needed fields for each employment type) and potential validation rules. The output schema exists, so return values are presumably covered. The description is reasonably complete but could add more usage context.

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 provides 100% coverage for all 27 parameters, with detailed descriptions for each. The description adds minimal param guidance: it clarifies that 'sonstige' uses 'bruttoGehalt' and that the calculation is based on current PAP, but does not explain all parameters. Since coverage is full, the baseline is 3 and the description adds modest value.

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 it calculates base salary, gross, net, and special payments from core data, distinguishing between tariff/Beamte and 'sonstige' modes. However, the German acronyms (DIREKTBERECHNUNG & BRUTTO-NETTO-RECHNER) may be confusing, and the purpose is not explicitly differentiated from sibling tools like calculate_agent_salary.

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 it supports multiple employment types and covers both gross-net calculation and tariff/Beamte modes, but it does not explicitly state when to use this tool over calculate_agent_salary or get_public_sector_options. No exclusion criteria or explicit alternatives are given, so the agent must infer usage from the tool name and siblings.

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