ebay_bulk_create_ads_by_inventory_reference

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

The annotation only declares readOnlyHint: false, indicating a write operation. The description adds 'create' but gives no further behavioral context: it does not mention whether the operation is idempotent, what happens to existing ads, rate limits, or the response format. For a bulk write operation with no other annotations, this is a significant transparency gap.

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, direct sentence that states the action and resource without extraneous detail. It is concise and appropriately sized for the tool's complexity.

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?

The tool is a bulk operation with nested objects and no output schema. The description omits key contextual information: it does not mention that the request array can contain multiple items, any constraints on the number of items, whether the campaign must be active, or how errors are reported. Given the complexity and lack of annotation support, the description is incomplete for an agent to use it correctly without further investigation.

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 has 100% description coverage: campaignId is described as 'campaignId required endpoint parameter' and request as 'Bulk create ads by inventory reference request body'. These schema descriptions are minimal but exist. The tool description adds nothing about the parameters—it does not explain the structure of the request array or the meaning of fields like bidPercentage or inventoryReferenceType. With schema coverage at 100%, the baseline is 3, and the description does not add value beyond the schema.

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 (Bulk create) and the resource (ads by inventory reference). The term 'Bulk' distinguishes it from single create tools like ebay_create_ads_by_inventory_reference, and 'by inventory reference' distinguishes it from bulk create by listing ID (ebay_bulk_create_ads_by_listing_id). However, it does not explicitly compare itself to these siblings, leaving some ambiguity for an agent that must choose between them.

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 the single create or the listing-ID variant. It does not state prerequisites (e.g., campaign must exist), nor any conditions under which this tool should be avoided. An agent has to infer usage from the name alone, which is insufficient given the large number of related ad tools.

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