samsara_get_vehicle

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

No annotations are provided, so the description carries the full burden. It only says 'detailed information' without specifying what that includes (e.g., make/model, VIN, current odometer, gateway status). It does not state if this is a read-only operation or if it might trigger side effects.

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, compact sentence that efficiently conveys the core purpose. Every word carries meaning.

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 no output schema and no behavioral annotations. The description is too vague for a 'get detail' tool; it should at least enumerate the key categories of information returned. Without output schema, the agent has no clue what 'detailed information' means.

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?

Only one parameter exists, and schema coverage is 100%. The schema already describes vehicleId as 'The unique ID of the vehicle'. The description adds no extra semantics but the schema is sufficient.

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 uses a clear verb 'Get detailed information' and identifies the resource 'specific vehicle by ID'. It is distinct from its siblings like samsara_list_vehicles (list vs detail) and samsara_get_vehicle_locations (general info vs location-specific).

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 guidance is provided on when to use this tool versus alternatives. For example, it doesn't explain that this returns static vehicle details while samsara_get_vehicle_locations returns location tracking or samsara_get_vehicle_stats returns aggregated statistics.

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