ebay_create_inventory_task

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

Beyond the single readOnlyHint=false annotation, the description discloses the asynchronous nature, the HTTP 202 response, that the call returns taskId and Location, and the required sell.inventory OAuth scope. These are exactly the behavioral traits an agent needs and they are not derivable from the annotation or schema.

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?

Information-dense and front-loaded: the purpose and feedType lead, followed by response behavior and the follow-up tool chain. It is somewhat run-on with heavy punctuation, but virtually every clause carries actionable content and there is no filler.

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 an async, nested-object write tool with no output schema, the description covers the essentials: what it creates, the required literals, the 202/taskId return shape, the polling and download steps, and the required scope. Nothing critical to calling it correctly is missing.

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 nested task schema already documents feedType, schemaVersion, and filterCriteria.listingFormat. The description corroborates the literal required values (schemaVersion 1.0, the only supported feedType, AUCTION/FIXED_PRICE) but adds no syntax or semantics beyond what the schema states, so baseline 3 applies.

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?

States a specific verb (Create) plus the exact resource (asynchronous Feed API ActiveInventoryReport task) and even summarizes the report contents (price and quantity of every active listing). This clearly separates it from the many other task-creation siblings by naming the concrete feedType LMS_ACTIVE_INVENTORY_REPORT.

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 lays out the operating workflow explicitly: eBay returns 202, then poll ebay_get_inventory_task, then download via ebay_get_feed_task_result_file. That is strong when/how-to-proceed guidance. It stops short of excluding or comparing against other task-creation siblings (ebay_create_feed_task, ebay_create_report_task), so it is not a full 5.

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