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

No annotations are provided, so the description must carry the behavioral disclosure burden. It states a constraint ('Only available for automotive clients') but does not mention read-only nature, required permissions, rate limits, or what happens if VIN/stock_number is omitted—only that one is used. It also doesn't clarify whether 'full details' includes specific fields.

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 two concise sentences, front-loaded with the primary action and resource. Every word adds meaning, with no filler or repetition of schema details.

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 3-parameter tool with no output schema and no annotations, the description is minimally adequate. It communicates the core purpose and a key restriction, but lacks detail on return format (what 'full details' includes), error behavior, or prerequisites beyond automotive client status. More completeness would be expected given the absence of an output schema.

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 coverage is 100%, so baseline is 3. The description adds semantic value by stating the vehicle is identified by VIN or stock number, implying a logical either/or relationship that the schema doesn't enforce. It also ties client_slug to the automotive-client restriction.

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 ('Returns') and a specific resource ('full details for a specific vehicle') while naming the lookup keys ('by VIN or stock number'). This clearly distinguishes it from sibling tools like get_product_details and search_inventory.

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: use when needing full details for one specific vehicle. The phrase 'Only available for automotive clients' gives a context restriction, but there is no explicit when-not-to-use or comparison with alternatives like search_inventory.

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