Prepare T2 Corporate Tax Worksheet

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

With no annotations, the description carries the full burden. It states it 'reviews all transactions, applies tax adjustments, and calculates tax owing,' which gives insight into internal processing. However, it doesn't disclose whether the worksheet is saved, permissions needed, or any side effects, so it's not fully transparent.

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?

Three sentences, each earning its place: first states the core action, second explains the user benefit, and third describes the process. No redundancy or fluff.

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 2-parameter tool with no output schema, the description adequately explains the purpose, process, and outcome. It lacks details on the exact output format or edge cases, but is sufficient for a worksheet preparation tool.

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 description coverage is 100%, so both parameters (fiscal_year and additional_adjustments) are already documented. The description adds context by mentioning 'applies tax adjustments' and 'bookkeeping data,' but doesn't provide new syntax or format details 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 uses the specific verb 'Compile' and clearly identifies the resource: 'T2 corporate income tax return worksheet' from 'bookkeeping data.' It also mentions generating numbers for CRA, which distinguishes it from siblings like prepare_gst_worksheet and calculate_corporate_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 context is clear: it's for preparing a corporate T2 worksheet from bookkeeping data for CRA filing. It doesn't explicitly state when not to use or name alternatives, but the T2 focus and mention of 'reviews all transactions' implies a comprehensive corporate tax preparation scenario.

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