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

No annotations exist, so the description carries the full burden and does useful work: it discloses that records are synthetic (method 'synthetic') with per-value provenance, and explains what listing.selling_location contains (link_status, selling_location_id, candidates, flags like group_site_lists_sister_store/multi_store_unstated). It omits error/missing-listing behavior and any auth or rate-limit context.

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 opening sentence front-loads what the record is and its provenance, and every following clause adds concrete field-level information rather than filler. It is dense with nested parentheticals, which costs some readability but no sentence is wasted.

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 describing the record's key sub-structures (selling_location link, dealer block) and routing price/fee questions elsewhere. It still leaves the overall response shape and failure modes unstated, so it is strong but not exhaustive for a record-retrieval tool.

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 parameter is fully documented there. The description restates the same listing_id format (dealer_key:VIN or urn) without adding syntax, validation, or format detail beyond the schema, so the baseline of 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 states a specific resource and scope: a full synthetic listing record with per-value provenance, retrieved by listing_id. It distinguishes itself from get_price_breakdown (compact price/fees) and anchors listing_id to search_inventory, so an agent can tell it apart from its siblings without opening a schema.

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 names one alternative with an explicit selecting condition ('For price and fees in a compact form, use get_price_breakdown') and implies the upstream flow via 'as returned by search_inventory'. It does not state when this tool is the wrong choice beyond price lookups, so it stops short of full when/when-not coverage.

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