calculate_distance_securite

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

With no annotations, the description carries the burden. It discloses the rule applied (2-second, 3-second for highway) and return fields, but does not mention idempotency, side effects, or authentication needs. It is adequate for a calculator but not rich.

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: first covers purpose, second covers return format and related resources. No wasted words. Front-loads the key action.

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 one-parameter calculator with an output schema hinted, the description is mostly complete: it explains what it does, what it returns, and points to related tools. Lacks details on return note field or edge cases, but overall sufficient.

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 parameter description in schema already says 'Vehicle speed in km/h'. The description adds no new meaning to the parameter, only context about the rule. 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?

The description clearly states the verb 'Calculate' and specific resource 'safe following distance using the 2-second rule (French highway code)'. It distinguishes from sibling distance tools like calculate_distance_2d or calculate_braking_distance by focusing on following distance with a specific rule.

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 implies when to use (need safe following distance) and points to list_bundles for related 'auto-transport' calculators, but does not explicitly state when not to use or compare to alternatives like braking distance or other distance types.

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