ebay_bulk_update_keyword

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

No annotations provided, so the description must fully disclose behavior. It merely states the action without detailing what happens during the update (e.g., whether existing values are overwritten, required permissions, idempotency, or error handling). This is insufficient for a mutation tool.

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 very short (one sentence), but it is to the point. However, it lacks structure and could be expanded with minimal effort to include key behavioral notes without becoming verbose.

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 complexity (nested objects, bulk operation) and lack of output schema, the description is incomplete. It omits important context such as maximum batch size, rate limits, response format, and whether partial updates are supported.

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 the schema already documents parameters. The description adds no additional meaning beyond the schema fields. It does not explain the nested request structure or provide examples, which would be helpful for an API with nested objects.

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 'Bulk update keyword' clearly identifies the action (bulk update) and the resource (keyword). It distinguishes from siblings like ebay_update_keyword (single) and ebay_bulk_create_keyword (bulk create), though it doesn't explicitly contrast 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?

No guidance on when to use this tool over alternatives. For example, it does not specify that this should be used for updating multiple keywords at once versus ebay_update_keyword for single updates. No context on batch size limits or prerequisites.

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