ebay_bulk_update_keyword

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

Annotations only provide readOnlyHint=false, which aligns with the mutating nature of 'update' but adds little. The description does not disclose whether the update replaces the entire keyword object, whether bid and keywordStatus are independently updatable, whether partial failures occur, or what the response contains.

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, front-loaded sentence with no filler or repeated structured data. It is concise, though 'through the eBay Marketing API' is somewhat redundant given the tool name and adds little value.

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?

For a mutating tool with no output schema and sparse annotations, this description is incomplete. It does not explain what campaignId/request mean behaviorally, what keywordStatus values are valid, whether campaign state matters, or when to prefer this over ebay_update_keyword. The schema alone provides only minimal context.

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%, so the parameter names and top-level descriptions already carry most of the load. The tool description adds no additional parameter information, and nested fields like keywordStatus, bid.value, and bid.currency lack explanatory detail, but the schema baseline of 3 is appropriate.

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 concrete action ('bulk update') and a specific resource ('keyword'), so an agent can tell it performs bulk keyword modification. However, it does not explicitly distinguish itself from close siblings like ebay_update_keyword or ebay_bulk_create_keyword, and it omits which keyword attributes can be updated.

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_update_keyword for a single keyword or ebay_bulk_create_keyword for creation. The word 'bulk' implies multiple updates, but the description never states this selection criterion or any exclusions.

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