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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safe read profile is covered. The description adds that results are 'normalized vehicle summaries' with a 'total matching count', which is useful contextualizing, but nothing about pagination limits beyond the schema.

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?

A single front-loaded sentence that names the resource, the filter surface, and the return shape with no filler. Efficient, though terse enough that slightly more context could be added without bloat.

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?

With an output schema present, the return values are covered elsewhere, and annotations carry the safety profile. The description plus schema is largely sufficient for an agent to call this search correctly; only alternative-tool routing is missing.

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 the schema already documents all 15 parameters including codes, enums, and defaults. The description's mention of make/model/price/year/mileage filters merely echoes a subset of what the schema states in more detail.

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?

States a specific verb and resource ('Autotrader vehicle listing search') plus the filter dimensions covered, so an agent can recognize it as the search entry point of the Autotrader family. It does not explicitly name sibling tools like autotrader_vehicle, so it stops short of full differentiation.

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 is implied by the name and description (search listings), but there is no explicit when-to-use guidance or pointer to alternatives such as autotrader_vehicle for detail lookups. Nothing misleading, just no routing help.

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