calculate_property_tax_estimate_fr

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the tool 'estimates' and returns specific fields, offering no information about side effects, permissions, data sources, or accuracy. For a calculation tool, basic safety aspects are missing.

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 one sentence plus return object and cross-reference. It is front-loaded with purpose and avoids fluff. However, it could be slightly more informative without being verbose.

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 two-parameter calculation tool with an output schema described, the description covers essential functionality and hints at related tools. It sufficiently informs an agent about what the tool does and returns.

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?

Input schema has 100% coverage with clear descriptions ('Valeur locative cadastrale EUR', 'Commune tax rate percent'). The description minimally restates these. Since schema coverage is high, baseline is 3; the description adds no significant extra meaning.

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 estimates French taxe foncière from cadastral value and commune rate, and specifies the return object. However, it does not explicitly distinguish this tool from other French property tax calculators in the sibling list, such as calculate_property_capital_gains_fr or calculate_property_transfer_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?

No guidance on when to use this tool over alternatives, nor any prerequisites or exclusions. The only mention is a cross-reference to list_bundles for related calculators, which is indirect and insufficient for an agent to decide when to invoke this tool.

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