List vehicles

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

With no annotations provided, the description carries the behavioral transparency burden. It discloses that the tool returns the entire fleet by default and is auto-paginated, which is useful context not present in the schema. It does not cover response shape or data freshness, but for a read-style listing tool the disclosure is solid.

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?

Three tight sentences: source and content first, then default behavior and pagination, then the intended use case. Every sentence earns its place and there is no filler.

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 an all-optional-parameter list tool, the description provides the source, default behavior, pagination behavior, representative return fields, and a concrete use case. The missing output schema is partially offset by listing returned fields, though an explicit statement that all six properties act as optional filters would make it fully complete.

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 only 33% (2 of 6 parameters documented). The description does not compensate: it only says 'No filtering by default' and never explains the other filter parameters (colour, model_year, manufacturer, chassis_number) or how filters combine. Low coverage with no compensating detail leaves the agent guessing.

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 specific verb and resource: 'Full Procon fleet vehicle list from Cartrack', and enumerates the returned content (registration numbers, vehicle IDs, make/model, maintenance status). It is clearly distinct from siblings like get_vehicle_status, get_trips, and get_fuel_data.

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 gives an explicit use case: 'Use this to match against the Fleet Register.' It also clarifies the default behavior (no filtering, whole fleet, auto-paginated). It does not explicitly name alternatives or when-not-to-use cases, so it falls just short of a 5.

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