calculate_french_income_tax

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

No annotations are provided, so the description carries the full burden. It describes the calculation method and return fields but does not disclose any side effects, limitations, or preconditions (e.g., whether income must be net taxable, what happens with zero income).

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?

Two sentences, the first defines action and method, the second lists return fields. No unnecessary words, front-loaded with key information.

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?

With an output schema existing, the description needn't detail return values, but it fails to address edge cases or clarify the meaning of 'family_quotient' in the output. Adequate but not thorough for a tax calculation 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?

Schema coverage is 100% and descriptions are already present. The description adds 'family quotient system' context for the 'parts' parameter but does not significantly enhance understanding beyond the schema's 'fiscal shares' description.

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 'Calculate French income tax (IR) for 2026 using progressive brackets per Article 197 CGI with family quotient system.' This specifies the exact resource and verb, distinguishing it from siblings like calculate_belgian_income_tax or calculate_french_salary.

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 only mentions 'See list_bundles for related finance-france calculators' as a reference to related tools but does not provide explicit guidance on when to use this tool vs alternatives or when not to use it.

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