ebay_create_ads_by_inventory_reference

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

No annotations are provided, so the description carries the full burden. It only states the basic function without disclosing side effects, permissions, rate limits, error handling, or lifecycle behavior. This is insufficient for a create operation.

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 sentence that conveys the essential information without any fluff or unnecessary words. It is maximally concise.

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 of nested objects and the absence of an output schema, the description is incomplete. It does not explain what the tool returns (e.g., success indicators, ad IDs), prerequisites (campaign must exist and be CPS), or error behaviors. More context is needed for an agent to use it confidently.

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?

The input schema has 100% description coverage, so the schema already documents the parameters. The description adds the 'CPS campaigns only' constraint, which is not in the schema, slightly enriching beyond the baseline. However, no additional meaning for individual parameters is provided.

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 ads) and the method (using Inventory API references), and specifies a constraint (CPS campaigns only), which helps distinguish from other ad creation tools. However, it doesn't explicitly differentiate from similar tools like 'ebay_create_ad' or the bulk version.

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 only provides a constraint ('CPS campaigns only') but fails to give any guidance on when to use this tool versus alternative ad creation tools (e.g., bulk, by listing ID). No explicit when-to-use or when-not-to-use directives are present.

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