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

With no annotations, the description carries the full behavioral burden and does so well: it states that the tool takes no buyer inputs, computes no tax amounts or total, and that a dealer-advertised monthly payment is ad text rather than a calculation. It also describes output structure details such as price_component labels, source_text, method_text, and tax_treatment metadata.

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 front-loaded with the primary purpose and remains dense with useful details rather than filler. It is somewhat long and clause-heavy, but the length is justified by the complexity of the output and the need to route the agent to adjacent tools.

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?

Given the lack of an output schema and annotations, the description is complete enough for an agent to call the tool correctly. It explains the returned price components, fee and incentive treatment, tax-rule checks, and the distinction between published ad text and calculated amounts.

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?

The schema already provides 100% description coverage for listing_id, including its dealer_key:VIN format from search_inventory. The description reinforces that the tool operates on ONE listing but does not add new syntax or meaning beyond the schema, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: seeing what the dealer lists for ONE listing as published, including headline price, MSRP, fees, incentives, and tax/fee rules. It clearly distinguishes this tool from estimate_out_the_door and get_payment_estimate by naming those siblings and describing their different purposes.

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?

It explicitly says to use this tool to see the dealer's published listing breakdown, then directs the agent to use estimate_out_the_door next for the buyer's total and get_payment_estimate for a monthly payment. It also explains conditional incentive handling, including passing label_raw values only if the shopper qualifies.

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