calculate_speed_distance_time

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

With no annotations, the description must disclose behavioral traits. It mentions 'Returns: {error}' but does not explain the output format or potential error conditions. More detail on the return value and behavior for invalid inputs is needed.

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 consists of two short sentences. The first defines the tool's purpose and usage. The second directs to related tools. No redundant information is present.

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?

The tool is simple and the input schema is fully described. An output schema exists, so return values need not be detailed. However, the description could mention the formula or note that negative inputs are handled, but it is adequately complete for typical use.

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 input schema provides descriptions for all three parameters (units: km/h, km, minutes). The description adds that exactly two must be provided, which is not enforced by the schema. This enhances understanding despite full 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?

The description clearly states the tool's function: solve for speed, distance, or time given any two of the three values. It also mentions a related tool category ('sport' calculators in list_bundles), distinguishing it from sibling tools.

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 explicitly says to provide any 2 of 3 values, which tells when to use it. It also directs to list_bundles for related calculators, offering alternatives. However, it does not specify when not to use it or clearly exclude other similar tools.

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