samsara_get_vehicle_locations

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions a feed API pattern for streaming but does not explain rate limits, authentication needs, how recent the data is, or whether it returns only currently active vehicles. Significant gaps remain for an agent to understand side effects or constraints.

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?

Two sentences with no wasted words. The purpose is front-loaded and the streaming pattern is explained efficiently. Every sentence adds value.

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?

For a tool with two parameters, no output schema, and no annotations, the description covers the core purpose and data type. It could benefit from mentioning pagination or iteration behavior for the feed API, but is largely sufficient for a simple location-streaming tool.

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?

Input schema has 100% coverage with descriptions for both parameters. The description adds minimal value beyond the schema—'real-time or recent' and 'feed API' do not elaborate on parameter behavior (e.g., what 'after' means in a streaming context). Baseline 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 gets real-time or recent locations for vehicles and mentions the feed API pattern for streaming. This distinguishes it from sibling tools like samsara_get_vehicle (single vehicle details) and samsara_get_vehicle_stats (statistics), making the purpose specific and unambiguous.

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 use for streaming location data but does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The sibling tools exist but no comparative guidance is provided.

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