get_ebay_item

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Get current details.' It implies a read operation but does not state output behavior, error cases, authentication requirements, or rate-limit implications, so an agent gets little behavioral context beyond the action verb.

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 a single front-loaded sentence with no filler. It communicates the action, scope, and parameter type in minimal words.

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?

This is a simple one-parameter lookup tool with no output schema, and the description provides the essential information: the endpoint domain (eBay Browse API), the resource, and the required identifier. It does not explain return values, but 'current details' is reasonably sufficient for a basic get-by-ID operation.

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?

The input schema only defines itemId as a string, and schema coverage is 0%, so the description must add semantic meaning. The phrase 'eBay Browse API item ID' clarifies that the string is an eBay Browse API identifier rather than a generic ID, but it does not describe format, source, or examples.

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 action ('Get current details') on a specific resource ('a specific eBay Browse API item ID'), so it is clearly more than a tautology. It is identifiable against the broader tool set, though it does not explicitly name any sibling it should not be confused with, such as get_listing.

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 implies the tool is for looking up a single eBay item by ID when current details are needed, which is an implied usage context. There is no explicit guidance about when not to use it or which alternative, such as get_listing or search_ebay_vinyl, should be chosen instead.

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