trips

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

With no annotations, the description carries the full burden. It usefully discloses the detection method (timezone-based) and comparison baseline (30 home days before each trip), but omits data requirements, permissions, and return structure.

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 efficient sentence with no wasted words and front-loads the core purpose. It could be slightly clearer if the comparison and output clauses were structured separately, but it remains appropriately sized.

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 core analysis is described, but important gaps remain: min_days is unexplained, no data prerequisites are stated, and there is no indication of what the response looks like despite having no output schema. An agent would need to infer usage and parameter behavior.

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 only parameter, min_days, has 0% schema description coverage and is never mentioned in the description. The description therefore fails to compensate for the low schema coverage and leaves the parameter's meaning unexplained.

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 states a specific analytical resource: trips detected from phone timezone, each compared to 30 prior home days, with travel effects on steps, sleep, and heart rate. It implicitly distinguishes itself from detect_locations by saying no location data is needed, though it does not name that sibling explicitly.

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?

There is no guidance on when to use this tool versus alternatives such as detect_locations or other trend tools. It also does not state prerequisites like ingested data or timezone availability.

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