ebay_create_ads_by_inventory_reference

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

No annotations present, and description only states the action. Does not disclose side effects, permissions, destructive nature, rate limits, or any behavioral traits.

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?

One sentence, no fluff, but it is too minimal. Could include more structure without being 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?

Despite schema coverage, the tool has a nested object and no output schema. Description lacks behavioral info, return value, error handling, and completeness for agent decision-making.

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 baseline is 3. Description adds no extra meaning beyond the schema descriptions. Does not explain bidPercentage format or inventoryReferenceType values.

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?

Description clearly states the action (Create ads) and method (by inventory reference) and API (eBay Marketing API). It distinguishes the resource but does not differentiate from sibling tools like ebay_create_ad_by_listing_id or ebay_bulk_create_ads_by_inventory_reference.

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 vs alternatives (e.g., bulk version, listing ID version). No prerequisites or context provided.

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