calculate_pinel_tax_reduction

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

With no annotations provided, the description must fully disclose behavior. It explains that the tool computes a tax reduction and returns total and yearly amounts, but does not mention any side effects, prerequisites, or constraints beyond the schema (e.g., investment cap of 300k).

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 three sentences, front-loading the purpose and usage. The second sentence ('Use to evaluate...') is somewhat redundant with the first, but overall concise and well-structured.

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 presence of an output schema (confirmed by context signals), the description covers inputs and outputs adequately. It mentions the return format (total and yearly amount), complementing the schema. No further details are necessary for a simple calculator 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%, so the description adds limited value beyond the schema. It reiterates the inputs and adds the output structure (total and yearly reduction), which is not in the schema, but this is minor for a calculator tool.

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 verb 'Compute' and the resource 'French Pinel rental investment tax reduction (rates 2026)', distinguishing it from other calculators by referencing 'list_bundles' for related tools. It also specifies the use case for evaluating Pinel real estate investment savings.

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 lists the inputs and outputs, providing clear usage context, but does not explicitly state when to use this tool versus alternatives or provide exclusions. The reference to 'list_bundles' is indirect guidance.

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