ebay_bulk_create_ads_by_inventory_reference

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

No annotations are provided, so the description must fully disclose behavior. It only states the creation action without detailing side effects, error handling, idempotency, or authentication requirements, leaving significant gaps for an agent.

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 sentence, which is concise but underspecified. It front-loads the purpose but omits critical details, making it borderline between efficient and insufficient.

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?

Given the tool's complexity (nested objects, no output schema, no annotations), the description is too minimal. It fails to explain return values, error scenarios, or limitations, leaving the agent with inadequate context for correct invocation.

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%, so baseline is 3. The description adds minimal value by referencing 'SKU/inventory item group key,' but the schema already describes this. No additional semantic clarification is provided beyond what the schema offers.

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 creates multiple ads using Inventory API references, specifically SKU or inventory item group keys. It also notes the restriction to CPS campaigns, which distinguishes it from siblings like 'ebay_bulk_create_ads_by_listing_id' and 'ebay_create_ads_by_inventory_reference'.

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 explicitly states 'CPS campaigns only,' providing a clear context for when to use this tool. However, it does not mention when not to use it or suggest alternatives for other campaign types, limiting complete guidance.

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