get_vehicles

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

With no annotations provided, the description carries the full burden. It discloses the effect of supplying location (distance annotation, sorting) and the default radius constant, and describes filter behavior. It does not mention authentication or rate limits, but for a read-only list tool this is acceptable.

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 well-structured in two paragraphs, front-loading the core purpose. Every sentence adds value, with no redundancy. At around 150 words, it is concise and easy to parse.

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?

Given the tool has 8 optional parameters, an output schema (so return values need not be detailed), and no required fields, the description fully covers behavior and all filters. It provides sufficient context for an agent to select and invoke the tool correctly.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter's purpose: location scoping with latitude/longitude, default radius via constant, branch_id, category_ids, exclude_stationed_vehicles meaning free-floating only, and min/max state_of_charge as battery percentage 0-100. This adds significant value beyond the schema titles.

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 opens with a clear verb+resource statement 'List available vehicles for the signed-in user.' It further explains location-based and non-location behavior, and lists all filters, making its purpose highly specific and distinct from sibling tools like create_rental.

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 explicitly states when to include latitude/longitude for spatial filtering and default radius behavior, and explains each filter's effect. However, it does not explicitly state when not to use this tool or directly contrast with siblings, leaving a minor gap.

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