run_ebay_product

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

With no annotations, the description carries the full disclosure burden. It does add genuinely useful behavioral context by stating the cost profile ('Flat 5 points per successful run'), which is more than most definitions provide, but it omits whether the call is read-only, what happens on an invalid ePID, or any rate-limit/error behavior.

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 short sentences, front-loaded with the core purpose and output fields, followed by a compact cost note. No filler and nothing repeated from the schema.

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?

There is no output schema, and the description compensates by listing the returned fields (brand, model, rating, price range, specs). For a simple single-parameter read tool with no annotations, that is close to sufficient; the main gap is the missing guidance on when to prefer this over sibling eBay tools.

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 the single parameter is already documented ('ePID or URL. e.g. 1234567890'). The description's 'by ePID' mildly narrows the accepted input versus the schema's ePID-or-URL, adding no new semantic detail, 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 names a specific verb ('Get'), a clearly scoped resource ('eBay catalog product details'), and an identifier ('by ePID'), and it enumerates the returned fields. It implicitly distinguishes itself from listing-oriented siblings like run_ebay_item or run_ebay_item_search by emphasizing 'catalog product', but it never names or contrasts those siblings explicitly.

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?

There is no when-to-use guidance, no prerequisites, and no reference to alternatives. An agent cannot tell from the text alone whether to reach for this versus run_ebay_item_search or run_ebay_item, particularly since 'ePID' vs 'item ID' is the only differentiator and it is not explained.

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