ebay_suggest_items

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states it returns suggestions without mentioning read-only nature, authentication needs, rate limits, or what happens if the campaignId is invalid. The description is insufficient for safe invocation.

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 sentences, no wasted words. It is front-loaded with the action and resource. Could be slightly improved by structuring into a bullet, but it is concise.

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?

No output schema is provided, and the description only vaguely says 'returns items that could perform well'. The agent needs to know the output format to use the results. For a suggestion tool, this is a significant gap.

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% with the parameter 'campaignId' described as 'Campaign ID'. The description adds minimal extra meaning beyond stating 'for a campaign'. Baseline of 3 is appropriate as schema already covers it.

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 tool gets item suggestions for a campaign and returns items that could perform well. The verb 'Get' and resource 'item suggestions' are specific, and it distinguishes from sibling suggestion tools like ebay_suggest_bids or ebay_suggest_keywords. However, it does not differentiate from ebay_find_listing_recommendations, which may be similar.

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 provides no guidance on when to use this tool versus alternatives like ebay_suggest_bids or ebay_create_ads_by_inventory_reference. There is no mention of prerequisites, context, or when not to use it.

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