List cars

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

readOnlyHint=true already tells the agent this is a safe read, so the bar is lower. The description does add genuine return-content context beyond the annotation: car-code-to-name mapping, 'driving sides on the interior pages', and a per-car unsaved-changes flag. It does not cover result size, ordering, or what happens when a page has no pictures — minor gaps given the read-only annotation.

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?

It is one sentence with no filler, but it is syntactically tangled — two parentheticals and a trailing clause ('each with its driving sides on the interior pages and whether it has unsaved changes') that force re-reading. Information is present but not front-loaded or broken into scannable pieces.

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 with one optional enum parameter and no output schema, the description does cover the shape of the returned items (code, name, driving sides, dirty flag). What it omits is the meaning of 'page' relative to the returned cars and any hint about result size or empty cases, leaving it merely adequate rather than 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 100% and the single 'page' parameter already carries an enum of eight page names plus a default. The description only says 'a page has pictures for' and adds no semantics about what a page represents or how the enum values differ. With the schema doing the heavy lifting, the baseline 3 applies.

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 conveys the resource (car codes such as 0203070200 = VW Golf 7 estate) and the scope (cars a given page has pictures for), but it is phrased as a noun fragment with no explicit verb and never contrasts itself with the obvious sibling list_images. An agent can guess it retrieves a list of cars, but the boundary against list_images/get_image is left to inference.

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?

There is no statement of when to call this versus alternatives, no prerequisite, and no exclusion. The sibling set contains list_images, get_image, status, and find_vehicle_messages, all plausible adjacent tools, yet none are referenced. The only usage hint is the implicit 'a page' scoping.

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