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

With no annotations provided, the description carries the behavioral transparency burden. It clearly states that this is a calculation tool producing tax, benefits, net cash, and breakeven rate outputs. However, it does not disclose key behavioral details such as reliance on default assumptions, tax jurisdiction applicability, or the fact that international FX drag and payment rails are part of the model. No contradiction with annotations exists.

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 a single dense sentence with no filler or redundancy. It front-loads the action ('Calculate'), specifies the comparison subjects, and ends with the key output. Every word contributes to the agent's understanding.

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 13-parameter tool with no output schema and no annotations, the description conveys the core purpose but leaves gaps: it does not explain the return format, the role of the many optional parameters, or the assumptions embedded in the calculation. It is adequate but not rich enough for a fully informed invocation.

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 92%, so the schema already documents almost every parameter. The description adds useful context around the contractorHourlyRate as the 'breakeven billing rate' but does not provide meaning beyond the schema's existing parameter descriptions. 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 names a specific verb ('Calculate'), a clear domain ('tax, benefits parity, net spendable cash between W-2 salaried employment and 1099 independent contractor billing'), and a concrete deliverable ('exact breakeven billing rate ($/hr)'). This clearly distinguishes it from siblings like scorp_optimizer or indian_income_tax.

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 strongly implies the intended use case: comparing W-2 vs. 1099 compensation and finding the breakeven rate. However, it does not explicitly state when to use this tool versus any alternative, nor does it mention any exclusions or scenarios where another sibling tool would be more appropriate.

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