calculate_property_transfer_tax

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

Description contradicts schema: claims inputs 'department' and 'type (new/old)' which are not in schema, and implies French-only while schema supports multiple countries. No annotations to compensate.

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?

Three sentences are brief but include inaccurate details that add confusion. Could be more concise and accurate.

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?

Output schema exists but description doesn't leverage it. The mismatch between description and schema leaves gaps about behavior for non-France countries. Incomplete for a tool with schema and no annotations.

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 has 100% coverage but description adds incorrect parameter info (department, type) and omits mention of country. This misleads the agent about actual inputs.

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 states it computes French property transfer tax, which is a clear verb+resource. However, the schema supports multiple countries (FR, BE, US, UK, DE), making the 'French' claim misleading. Purpose is recognizable but inaccurate.

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?

It says 'Use for property buyers' and references list_bundles for related calculators. This provides some context but no when-not-to-use or explicit alternatives. Limited guidance.

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