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

With no annotations, the description carries the full burden and does disclose substantive behavioral context: the media are self-generated SVG placeholders labeled DEMO, are not real car photos, and no video or 360 viewer exists. That is genuinely useful for an agent to avoid misinterpreting results. It remains silent on auth, rate limits, and pagination behavior, so it stops short of a 5.

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?

Two compact sentences front-load the resource identity, with the DEMO caveats following. The phrasing is slightly dense, but every clause carries information and nothing is padded.

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 sideless read tool with no output schema and no annotations, the description covers what the payload contains and flags its synthetic nature, which is the key risk an agent needs to know. Minor gaps remain around result volume and ordering, but nothing essential to correct invocation 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 all three parameters are already documented, including the limit range and type filter values. The description's mention of photo/video/spin echoes the types enum without adding syntax or format detail beyond the schema, so the baseline 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 identifies the resource clearly ('Media block for a listing') and enumerates what it contains (photo, video poster, spin, rights notes), which cleanly separates it from siblings like get_listing and get_dealer. The retrieval verb is only implicit in the fragment phrasing, but the resource and scope are unambiguous.

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 only implied: the listing_id format ('dealer_key:VIN from search_inventory') hints at the calling sequence, but there is no explicit when-to-use statement, no exclusions, and no comparison against alternatives such as get_listing.

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