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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds the organisational scope and the underlying GET endpoint, but it does not mention pagination behavior, authentication, rate limits, or return characteristics.

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 very short and front-loads the core purpose. The endpoint path is not strictly necessary for tool selection, but the overall wording is efficient and not padded.

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 simple read-only list tool with complete input schema coverage, the description is minimally adequate. However, it does not clarify return values or how the vehicle list differs from related vehicle-class or subcontractor listings.

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 description coverage is 100%, so page, per_page, and search_string are already documented in the schema. The description does not add further meaning about pagination or search semantics, which is acceptable given the complete schema.

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 states a specific verb and resource: list fleet vehicles of the organisation. It is clearer than a generic list tool, but it does not explicitly differentiate itself from close siblings such as limoexpress_list_vehicle_classes.

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 the tool is for listing fleet vehicles, but it gives no explicit when-to-use guidance, prerequisites, or alternatives. An agent must infer whether to use this versus list_vehicle_classes or other fleet-related list tools.

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