ebay_get_item_details

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

Annotations already indicate readOnlyHint=true, and the description adds useful behavioral context by naming the underlying API and enumerating the cleaned fields returned. It does not contradict the read-only annotation, and the extra detail helps the agent know what the operation returns.

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 compact and well-structured: purpose and input first, then API/source context, then return fields, then the sibling alternative. Each sentence earns its place and there is no filler.

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 single-required-parameter read-only tool with no output schema, the description is complete: it identifies the input, the source API, the returned fields, and the alternative tool when appropriate. An agent has enough information to select and invoke it correctly.

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 coverage is 100%, and the itemId parameter is already well documented in the schema. The description repeats the same provenance ('from ebay_find_active_items') but adds no new parameter-level meaning beyond what the schema provides, 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 clearly states the action ('Get full detail'), the resource ('one active eBay listing'), and the exact input type ('Browse RESTful item id'). It also names the sibling alternative (ebay_get_listing) for the seller's own listings, making differentiation explicit.

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 specifies when to use the tool: for active listings found via ebay_find_active_items, using the Buy Browse API. It also provides an explicit when-not condition and alternative: 'For the seller's own listings use ebay_get_listing (Trading) instead.'

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