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

No annotations provided, so description carries full burden. It discloses that it returns three fields but does not mention behavioral traits (e.g., read-only, no side effects, no auth required). For a simple calculator, this is minimally adequate but lacking transparency.

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 efficient sentences clearly stating purpose, inputs, and output. No excessive detail. Front-loaded and well-structured.

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 fields are fully listed. Given the tool's simplicity and full schema coverage, the description is complete enough. Could optionally explain 'taxe foncière' but domain-specific knowledge may be assumed.

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 covers both parameters with descriptions (cadastral value in EUR, commune rate as percentage). Description adds no new semantic meaning beyond restating 'from cadastral value and commune rate'. Baseline 3 due to high schema coverage.

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 it estimates French taxe foncière from cadastral value and commune rate. Verb 'Estimate' matches tool name. Does not explicitly differentiate from sibling 'calculate_property_tax_fr' but hints at 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?

Implies usage context (French property tax estimation) but offers no guidance on when to use this versus alternatives, nor prerequisites or exclusions. The reference to 'list_bundles' is too indirect.

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