ebay_bulk_create_keyword

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

The annotation readOnlyHint=false indicates a write operation, and the description confirms creation. However, the description adds no behavioral details beyond the annotation—no mention of side effects, rate limits, required permissions, or response behavior. The description does not contradict annotations, but it contributes minimal extra context.

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 concise sentence that front-loads the action and resource. There is no extraneous text or repetition, making it efficiently structured.

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 complex bulk operation with a nested request object, but the description provides no explanation of the inner fields (adGroupId, keywordText, matchType, bid) beyond what the schema offers. There is no output schema, so the response format is unknown. The tool would benefit from clarifying expected inputs and outcomes.

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 description coverage is 100%, and the schema already describes the request body and campaignId. The description adds no parameter-level details. Since the schema covers all parameters, the baseline of 3 is appropriate, though the description could have clarified nested field meanings.

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 a specific verb ('Bulk create') and resource ('keyword') through the eBay Marketing API. It is clear and distinct from single-keyword tools, though it does not explicitly name siblings like ebay_create_keyword or ebay_bulk_update_keyword. The 'bulk' qualifier provides adequate differentiation.

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?

There is no guidance on when to use this tool versus alternatives such as ebay_create_keyword for single creation or ebay_bulk_update_keyword for updates. The description only implies bulk usage without stating prerequisites, limits, or selection criteria.

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