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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by disclosing the exact BMF PAP methodology, the components included (Lohnsteuer, Solidaritätszuschlag, Kirchensteuer, Sozialabgaben), and the inclusion of selected allowances and state-specific family allowance. No contradiction with annotations.

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: a front-loaded purpose line and one detailed sentence on methodology. Every sentence adds meaningful information, and the structure suits a tool with 29 parameters without becoming bloated.

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 complex calculation tool, the description covers the core purpose, method, tax components, allowances, and special payments, while the output schema handles return-value details and annotations cover safety. The only notable gap is the lack of explicit guidance on when to choose this over calculate_standard_salary.

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 the schema already documents all 29 parameters. The description adds only general context about selected Zulagen-IDs and the state-specific Familienzuschlag, but does not enrich individual parameter semantics beyond what the schema provides. 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 and resource: 'Berechnet das exakte Brutto, Netto und die jährliche Sonderzahlung inklusive ausgewählter Zulagen-IDs und bundeslandspezifischem Familienzuschlag.' It clearly distinguishes itself from the sibling option-retrieval tools and from a standard salary calculator by emphasizing complete ÖD-Berechnung and BMF-PAP-based net calculation.

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 a clear context: use for complete German public-service salary calculation with allowances and exact tax/social deductions according to the BMF PAP. However, it does not explicitly contrast this tool with calculate_standard_salary or state when not to use it, leaving some differentiation to inference.

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