Upcoming CRA tax deadlines for Canadian freelancers / self-employed individuals (filing, payment, GST/HST, RRSP, quarterly instalments), each on its CRA effective date with the weekend next-business-day rule applied. Also available as a subscribable calendar feed.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max deadlines to return (default 10) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries full burden. It discloses the behavioral trait of applying 'the weekend next-business-day rule' to dates, which is beyond the input schema. However, it does not mention authentication, rate limits, or any side effects, but for a read-only tool these are less critical.
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 with no wasted words. It is front-loaded with the main purpose and includes an extra feature (calendar feed) without verbosity. Every sentence earns its place.
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 simplicity and lack of output schema, the description adequately covers what the tool returns (deadlines with weekend rule). However, it does not specify the response format or structure, which leaves some ambiguity for an AI agent.
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% for the single parameter 'limit', which already has a clear description. The tool description adds no additional meaning or context for this parameter, so baseline score of 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 tool returns 'upcoming CRA tax deadlines' for Canadian freelancers/self-employed, specifying types (filing, payment, GST/HST, etc.). It is specific about the verb (get) and resource (deadlines), and it distinguishes from sibling tools like estimate_self_employed_tax or gst_hst_registration_check which focus on calculations or registrations.
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 usage for obtaining tax deadlines but does not explicitly state when to use this tool versus siblings or provide any exclusion criteria. There is no guidance on prerequisites or context for use, only a listing of deadline categories.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool addresses a distinct aspect of Canadian self-employed tax: CPP contributions, full tax estimate, deadlines, GST registration, GST method comparison, and instalment plans. No overlap in functionality.
All names use lowercase with underscores, making them readable. However, they mix verb-noun patterns (e.g., get_tax_deadlines, estimate_self_employed_tax) with noun phrases (cpp_self_employed, instalment_plan), showing minor inconsistency from the ideal verb_noun standard.
Six tools is a well-scoped number for the domain. Each tool serves a necessary function without redundancy, covering major tax obligations for Canadian self-employed individuals.
The toolset covers core self-employed tax math: CPP, overall tax estimate, deadlines, GST registration and method comparison, and instalments. Minor gaps exist (e.g., detailed deduction calculators, T2125 support), but agents can work with the provided set.
