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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new context beyond that: it discloses a data-scope boundary ('never exposes dealer contact details or private/admin data') and sketches the return shape, which matters because no output schema exists. It stops short of describing the 'active' dealer precondition's failure mode.

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 sentences, each load-bearing: scope, return content, and privacy boundary. The most decision-relevant information (which dealer, what it returns) is front-loaded with 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?

With no output schema, the description compensates by sketching the return payload (dealer identity, canonical URL, compact listing summaries) and stating the privacy boundary. Gaps remain around the implicit result cap (limit max 10) and what happens for an inactive or unknown slug, but for a read-only listing tool this is close to sufficient.

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%, so the description carries the full burden, and it names only three of five parameters (dealer_slug, vehicleType, price filters) while adding no format, range, or default semantics. It adds slight meaning — dealer_slug must reference an 'active' dealer, prices are filters — but leaves limit and the enum's significance undocumented.

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 gives a specific verb+resource (list public stock) and constrains scope to 'one active RoamWorthy dealer by dealer_slug', which functionally separates it from the broad search_listings sibling. It does not explicitly name or contrast with any sibling, so an agent must infer the boundary rather than read it.

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 scope constraint ('one active dealer', 'current public stock') and the optional filters, but there is no explicit when-to-use statement, no when-not-to-use, and no named alternative such as search_listings or find_matching_vehicles. An agent can infer the context but receives no routing guidance.

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