calculate_notary_fees

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

No annotations provided; the description states it calculates fees and returns a JSON object, but does not mention any behavioral traits like side effects, authorization, or rate limits. For a pure calculation tool, this is adequate but not informative beyond the schema.

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, no wasted words: first states purpose and output, second points to related tools. Highly efficient.

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 tool with 2 parameters and an output schema, the description covers purpose and output structure, and mentions related bundles. It could clarify the meaning of 'ancien' vs 'neuf' but the schema enum descriptions likely suffice.

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 description coverage is 100%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions; it only adds a pointer to related calculators.

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 'Calculate French notary fees (frais de notaire) for a real estate purchase.' and includes the return structure, distinguishing it from siblings like calculate_notary_fees_detailed.

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 mentions 'See list_bundles for related finance-france calculators' but does not explicitly state when to use this tool vs alternatives or when not to use it. There is no differentiation from the sibling calculate_notary_fees_detailed.

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