get_travel_info

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

With no annotations provided, the description must carry the transparency burden. The verb 'Get' signals a non-destructive read operation, which is useful, but the description does not disclose any limitations, default behavior, or side effects. It is neither misleading nor exceptionally informative.

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 a single, direct sentence with no redundant terms or filler. It communicates the core purpose efficiently.

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 has 3 parameters, no output schema, and no annotations. The description covers the main function but omits the mode parameter's behavior and return format details. For a simple tool, it is adequate but leaves clear gaps given missing annotation support.

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 67% (origin and destination have descriptions; mode does not). The description adds no semantic value beyond the schema—'between two locations' merely restates origin/destination, and the 'mode' parameter is left unexplained in both description and schema. The default of walking is only in the schema, not the description.

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 uses a specific verb 'Get' with a clear resource 'travel time and distance between two locations.' It fully distinguishes the tool from siblings like weather or outfit recommendations, leaving no ambiguity about its function.

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 usage for travel-related queries but provides no explicit when-to-use guidance or exclusions. Given that sibling tools are unrelated, there is no direct alternative to contrast, so the guidance is merely implied rather than stated.

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