calculate_puissance_fiscale

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

No annotations provided, so description carries full burden. Discloses formula and return fields but does not mention edge cases (e.g., negative values, precision) or performance characteristics. Adequate for a simple 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?

Two concise sentences with the formula front-loaded, returning structure, and sibling reference. Zero waste.

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 calculation tool with full schema and output schema, the description is nearly complete. Missing potential caveats (e.g., rounding, invalid inputs) but sufficient for correct invocation.

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% (both parameters described). The description adds the formula, which clarifies how parameters are used, but does not add additional semantics beyond schema. Baseline 3 is appropriate.

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 calculates French fiscal horsepower using a specific formula (CO2/45 + (P_kW/40)^1.6) and returns two fields (cv_raw, cv_fiscaux). Distinguishes from related tools via reference to list_bundles for 'auto-transport' calculators.

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 directs to list_bundles for related calculators, implying this tool is for the specific fiscal horsepower calculation. Could be more precise about when to use vs other 'calculate_*' tools, but the reference suffices.

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