calculate_canada_federal_tax

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

No annotations are provided, so the description carries full burden. It discloses the key behavior (uses BPA deduction) and return fields, but lacks explicit statements about safety, side effects, or permissions. For a read-only tax calculator, it's adequate but not thorough.

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 concise with two sentences, front-loading the main purpose. The 'Returns' list is efficient. No wasted words, though the '...' is ambiguous. Overall well-structured for its simplicity.

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 the presence of an output schema (not shown), the description covers the essential purpose, parameters, return values, and hints at related tools via list_bundles. It is sufficient for an experienced user, though a beginner might want more context.

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 single parameter 'income_cad' is fully described in the schema with 100% coverage. The description adds minimal extra context (e.g., 'with basic personal amount deduction'), but does not significantly enhance understanding 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 states it calculates Canadian federal income tax with the basic personal amount deduction, using a specific verb and resource. It distinguishes itself from siblings like 'calculate_canada_combined_tax' by focusing solely on federal 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 implies use for Canadian federal tax calculations but does not explicitly state when to use this tool versus alternatives (e.g., 'calculate_canada_combined_tax'). It mentions related calculators via list_bundles but provides no direct exclusion criteria.

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