calculate_notary_fees_detailed

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

No annotations are provided, so the description carries the burden. It clearly indicates this is a calculation tool returning a breakdown, implying read-only behavior. No mention of side effects or auth, but adequate for a calculator.

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 concise sentences: first states purpose and components, second gives usage audience, third lists inputs and output. Front-loaded and every sentence adds value.

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 output schema exists, the description sufficiently covers purpose, inputs, output overview, and related tools. It is complete for a calculation tool of moderate complexity.

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 the description adds context: property_price is in EUR, type is 'new'/'old', department is optional and affects DMTO rate. It goes beyond the schema by explaining the effect of department.

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 provides a 'detailed breakdown of French notary fees by component' for property buyers, listing inputs (price, type, department) and outputs (total and per-component breakdown). It distinguishes from the sibling 'calculate_notary_fees' by emphasizing 'detailed' 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?

The description specifies use for property buyers in France and suggests consulting 'list_bundles' for related calculators. However, it does not explicitly contrast with the non-detailed version ('calculate_notary_fees') to guide selection between them.

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