ebay_create_keyword

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

No annotations are provided, so the description must convey behavioral traits. It only states it creates a keyword, but lacks details on whether it overwrites existing keywords, required permissions, rate limits, or return behavior. For a write operation with no annotations, 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 a single, concise sentence with no wasted words. It is front-loaded with the primary purpose. However, given the tool's complexity (nested object), it could include a bit more context without losing conciseness.

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 has three required parameters, a nested object, no output schema, and no annotations. The description does not explain success behavior, error conditions, or provide examples. It relies heavily on the schema, which is insufficient for an agent to fully understand usage.

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 all parameters are already documented. The description does not add extra meaning about parameter usage or relationships beyond what the schema provides. It is adequate but not enhanced.

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 ('Create'), the resource ('keyword'), and the context ('manual targeting in a CPC campaign ad group'). It differentiates from siblings like 'ebay_bulk_create_keywords' and 'ebay_create_negative_keyword' by specifying single creation for manual targeting.

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 implies use for manual targeting in CPC campaigns but provides no explicit guidance on when to use this tool vs alternatives such as bulk creation or negative keyword creation. No exclusions or prerequisites are mentioned.

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