calculate_property_tax_fr

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

Describes the tool as a computation returning annual tax due, implying read-only behavior. No annotations exist, so description carries the full burden; it adequately sets expectations for a stateless calculator without side effects.

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: first states purpose, second lists inputs, output, and reference to related tools. No fluff, fully front-loaded.

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 simple 2-parameter tool with an output schema, the description covers purpose, audience, inputs, and output. References related tools for additional context. No gaps identified.

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% with clear parameter descriptions. The description paraphrases the inputs ('cadastral rental value, commune rate %') but adds no new meaning beyond what the schema already provides. Baseline 3 applies.

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?

Clearly states 'Compute French taxe foncière (annual property tax)' with specific context for owners in France. Distinguishes from sibling tools like calculate_property_capital_gains_fr by focusing solely on taxe foncière and referencing related calculators via list_bundles.

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?

Explicitly says 'Use for owners of property in France' and mentions related calculators via list_bundles, implying alternatives. However, it does not explicitly state when not to use or compare with similar tools like calculate_property_tax_estimate_fr.

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