Deel Calculate Take Home Pay

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so safety context is covered. The description adds minimal behavioral context by framing the operation as a calculation that accounts for deductions, but it does not disclose return format, supported countries, or calculation assumptions.

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?

Two short sentences that each earn their place: the first states the core operation-galculation of take-home pay; the second gives direct usage guidance. No filler or repetition.

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 read-only calculator with fully documented parameters and annotations covering safety, the description is nearly complete. It omits specific return details diagnostic of the take-home amount, but that is largely inferable from the tool name and purpose.

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 fully documents salary, country, and currency. The description adds no additional parameter-level meaning beyond what the schema already provides, so 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 clearly states the verb and resource: calculate take-home pay for a salary in a country, and reinforces it with the 'net pay, take-home salary, or deductions' trigger phrases. It is sufficiently distinct from siblings like deel_calculate_employment_cost, though it does not explicitly contrast itself against that sibling.

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 explicitly says when to use the tool: 'Use when the user asks about net pay, take-home salary, or deductions in a country.' This is clear contextual guidance, but it does not mention when not to use it or name alternative tools for related calculations.

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