list_vehicles

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

No annotations exist, so the description carries the burden of behavioral disclosure. The verb 'List' and the listed output fields signal a read-only retrieval operation, but the description does not disclose filtering behavior, whether inactive vehicles are included by default, or pagination/ordering behavior.

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 focused sentence that front-loads the action and resource, then lists the key output attributes. There is no filler or redundant information.

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 list tool with two optional parameters and no output schema, the description covers the main output fields but omits parameter behavior and any filtering context. It is adequate for a basic call but not fully complete for an agent deciding how to invoke it with parameters.

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 0%, and the description does not explain depot_id or only_active. The parameter names are somewhat self-explanatory, but the agent receives no guidance about filtering semantics, the default of only_active, or how depot_id affects results.

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 specific verb and resource ('List fleet vehicles') and clarifies the output focus: capacity (kg/units), depot, and driver shift. This clearly distinguishes it from sibling tools like list_deliveries or plan_routes.

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?

Usage context is implied by the verb and resource, but the description does not explicitly state when to choose this tool over alternatives or mention any exclusions. Sibling tools such as list_deliveries are not referenced for comparison.

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