calculate_braking_distance

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

No annotations are provided, so the description carries the burden. It accurately describes the computation and output, but does not explicitly state that the tool has no side effects or permissions requirements, which is expected 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?

The description is two sentences long, front-loads the purpose, and provides additional context without unnecessary detail.

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 simplicity of the tool and the presence of input schema descriptions, the description adds usage context and cross-references. However, the incorrect mention of a reaction time parameter reduces completeness, and no details about the output schema are given (though it exists).

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?

The description adds some meaning by explaining inputs (speed km/h, road type) and output, but it incorrectly lists 'reaction time s' as an input parameter, which does not exist in the input schema. This discrepancy could mislead an agent into expecting a parameter that is not available.

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 tool computes reaction and braking distance based on road condition, and mentions its use for driver safety education. However, it does not explicitly differentiate from sibling tools (e.g., calculate_braquet) beyond its unique functionality.

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 indicates when to use the tool ('for driver safety education') and suggests related calculators via list_bundles. However, it lacks explicit guidance on when not to use it or how it differs from alternatives.

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