ebay_bulk_create_campaign_keyword

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

No annotations are provided, so the description carries full burden. It only states 'bulk create keywords' but does not disclose behavioral traits like idempotency, partial success handling, validation rules, maximum batch size, or whether existing keywords are overwritten. For a bulk creation tool, this is insufficient.

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 extremely concise (5 words) with no superfluous content. However, it may be too minimal for effective use, lacking critical context. It is front-loaded with the key action but sacrifices completeness.

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 object, 2 required params, no output schema), the description is inadequate. It does not explain the return value, error behavior, or limits. The schema covers parameter structure, but the description should provide more behavioral context for a bulk 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?

Schema coverage is 100% (both parameters documented), so baseline is 3. The description adds no additional meaning beyond the schema; it does not explain the structure of the 'keywords' object or the required fields like keywordText and matchType. The schema already provides descriptions for campaignId and keyword fields.

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 states 'Bulk create keywords at the campaign level,' which clearly identifies the action (create), resource (keywords at the campaign level), and scope (bulk). It distinguishes from sibling tools like 'ebay_bulk_create_keywords' (likely ad-level) by specifying 'campaign level,' but does not explicitly differentiate.

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?

No guidance on when to use this tool vs alternatives (e.g., 'ebay_create_keyword' for single keywords, or 'ebay_bulk_create_keywords' for ad-level). There are no prerequisites, context signals, or when-not-to-use instructions.

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