Complete Tax Filing Calendar

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

Given no annotations are provided, the description carries the full burden. It correctly implies a read-only operation via the verb 'Display' and describes the output structure (deadlines by category), but it does not disclose any caveats such as data source, update frequency, or whether the calendar is for a specific tax year.

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, front-loaded sentence with no extraneous information. It efficiently conveys the tool's scope and output organization.

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, single-parameter display tool, the description is mostly complete. It specifies the audience (Alberta businesses), the scope (annual), and the organization (category). It could be improved by stating what the returned output looks like (e.g., dates and deadlines), but the lack of an output schema reduces the burden.

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 input schema fully documents the single 'category' parameter with an enum and a clear description ('Filter by category or show all'). The description's mention of 'organized by category' aligns with the schema, so the description adds no significant meaning beyond the schema.

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's function: displaying a complete annual tax filing calendar for Alberta businesses, organized by category. It uses a specific verb and resource, and the scope ('Alberta businesses', 'annual') helps distinguish it from related tools like 'upcoming_deadlines', though it doesn't explicitly name alternatives.

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 provides no guidance on when to prefer this tool over the sibling 'upcoming_deadlines' or other calendar-related tools. It only describes what the tool does, not when it should be used or when an alternative is more appropriate.

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