Inspect an eBay listing

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

Beyond the readOnly/openWorld annotations, the description discloses what data may be included, what missing data means, what is not guaranteed, and that seller-provided description/aspects are untrusted. These are meaningful behavioral and safety caveats for interpreting the response.

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 and dense: identifier rules, included data, missing-data caveats, and trust warning all appear without redundant repetition. Every sentence adds information relevant to correct use.

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?

An output schema exists, so return structure need not be explained, and the description covers the main lookup semantics plus important data-quality caveats. The main gap is that marketplace_id is not addressed at all.

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 must compensate. It explains item_id vs legacy_item_id and the exactly-one constraint, but it says nothing about marketplace_id, leaving one of three parameters undocumented in both schema and description.

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: retrieve/inspect an exact eBay listing identified by item_id or legacy_item_id. It distinguishes this exact-listing lookup from searching, which helps separate it from the sibling search_ebay tool.

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?

The description gives a clear operational rule: supply exactly one of item_id or legacy_item_id. It does not explicitly name when to use this instead of search_ebay, but the exactness of the lookup makes the intended context clear.

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