Canadian Payroll Deductions Calculator

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states the subject matter (CPP, EI, income tax) and gives no insight into how calculations work, what inputs affect what, or any side effects or output format.

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 extremely brief, almost a fragment. While it avoids fluff, it under-specifies and does not provide enough structured information to aid an agent in understanding the tool.

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 has 5 parameters, no parameter descriptions, and no output schema, the description is inadequate. It provides no context about how to use the tool, what results to expect, or how the inputs map to the outputs.

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 has zero descriptions for its 5 parameters, and the description does not mention any parameter names or meanings. An agent cannot infer the purpose of eiExempt, cppExempt, payFrequency, or grossPerPeriod from the description alone.

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 identifies the tool as computing Canadian payroll source deductions for CPP, EI, and income tax. It distinguishes itself from sibling calculators like sales tax or inventory tools, though it lacks an explicit verb like 'calculates'.

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 no guidance on when to use this tool versus alternatives such as canadian-sales-tax-calculator or us-sales-tax-calculator. There are no exclusions, prerequisites, or contextual hints beyond the tool's name and terse description.

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