samsara_get_vehicle_stats

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only states that stats are 'get' operations, which implies read-only, but fails to mention potential rate limits, pagination behavior, whether data is aggregated or raw time-series, or what happens with invalid vehicle IDs. Given zero annotation coverage, this is insufficient.

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?

A single sentence that is front-loaded with the action and resource, followed by key examples. No unnecessary words or filler. Every part earns its place.

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 three required parameters and no output schema. The description covers the types of data returned but offers no information on response format, time range granularity, or error conditions. It is adequate for a basic understanding but incomplete for reliable invocation without additional context.

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 each parameter having a description. The description adds context by listing example stat types (odometer, engine hours, fuel usage), but does not add new meaning to individual parameters beyond what the schema already provides. Baseline of 3 is appropriate.

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 retrieves vehicle statistics over a time range, listing specific metrics (odometer, engine hours, fuel usage). This is a specific verb+resource combination that distinguishes it from siblings like samsara_get_vehicle (single vehicle details) and samsara_get_vehicle_locations (location data).

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?

No explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, limitations, or exclusions. While the examples (odometer, engine hours) hint at time-series data, the agent is left to infer usage context without direct comparison to sibling tools.

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