tool_calculate_jet_lag

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

No annotations are provided, so the description carries full burden. It discloses that the tool gives a science-based schedule and tips, but does not state whether it is read-only or if it modifies any state. The behavior is implied as informational, but not explicitly described.

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 concise: two sentences for purpose followed by a bulleted list of arguments. No unnecessary words. Front-loaded with the main purpose and output scope.

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 moderate complexity and no output schema, the description adequately explains that the output includes jet lag severity and a recovery schedule covering pre-departure, on-plane, melatonin, and light exposure strategies. However, it does not mention what fields the output object contains, leaving some ambiguity for agent consumption.

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 descriptions are absent (0% coverage), so the description adds meaning by explaining each parameter: origin/destination as 'City or IATA code', departure_date as 'YYYY-MM-DD', and flight_duration_hours as 'Flight time in hours (0 = auto-estimated)'. This clarifies input formats beyond just field names.

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 calculates jet lag severity and provides a recovery schedule, using specific verbs and resources. It is distinct from sibling tools like tool_plan_itinerary or tool_search_flights, as it focuses solely on jet lag.

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 when traveling across time zones by mentioning pre-departure and post-arrival strategies, but it does not explicitly state when to use it over alternatives or provide exclusion criteria. No guidance on prerequisites or limitations.

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