Get trips

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a simple summary by revealing the 24-hour default, the 31-day request cap with automatic chunking, and the critical API limitation that fleet-wide queries cannot be filtered by vehicle. These are non-obvious behaviors an agent must know to use the tool correctly.

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 dense but well-organized, front-loading the returned fields before explaining defaults, limits, and filtering behavior. Every sentence contributes essential information, and no filler or tautology 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 description covers the returned data, default range, maximum range behavior, and the single-vehicle vs fleet distinction. Given the schema fully documents parameter formats and defaults, there is little else an agent needs to invoke the tool correctly. Even with no output schema, the listed fields effectively communicate the expected return contents.

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 already covers all four parameters with 100% coverage, setting a baseline of 3. The description adds meaningful context for the registration parameter, explaining the fleet-wide filtering limitation and how passing registration switches to a single-vehicle query. This adds value beyond the schema without duplicating it.

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 identifies the tool as retrieving trip history for a date range and enumerates the exact data types returned: route, distance, duration, idle time, and driving behavior. This distinguishes it from siblings like get_vehicle_status, list_vehicles, and get_fuel_data, all of which serve different data needs.

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 provides clear context for when to use the tool: for historical trip data over a date range, with default behavior and the 31-day cap explained. It also gives usage guidance for the registration parameter to query a single vehicle instead of the fleet. However, it does not explicitly name sibling tools as alternatives or state when not to use this tool.

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