leave_by

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

No annotations provided, but description discloses return fields (leaveByLocal, arriveByLocal, durationMin, distanceKm), no-live-traffic notice, and gives an example output. Adequately describes behavioral traits.

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?

Single paragraph with all essential info, example included. Could be slightly more structured (e.g., bullet points), but very efficient and clear.

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?

Covers purpose, parameters, return fields, and example. No output schema, but description sufficiently details outputs. Missing edge cases like timezone handling, but adequate for a convenience tool.

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% with descriptions. Description adds extra meaning: 'from' and 'to' accept Danish place names or lat,lon, 'arriveBy' format options, bufferMin default. Adds value beyond schema.

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's a convenience tool for calculating leave time given destination and required arrival time, distinguishing it from sibling drive_time by requiring explicit arriveBy parameter.

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?

Provides clear usage context: given destination and required arrival time. Compares to drive_time with arriveBy, but lacks explicit when-not-to-use or alternatives beyond the sibling comparison.

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