Seller create listing

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

Beyond the annotations (which only indicate non-read-only and non-destructive), the description reveals important side effects: the restricted-goods classifier runs at write time, and flagged listings are inserted but invisible until cleared. This is critical behavioral info that the annotations do not provide.

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 compact and to the point, consisting of two sentences. It avoids unnecessary details and focuses on the essential action and notable behaviors, making it easy to parse.

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 description covers the core action and a key behavioral nuance, but it does not mention what the tool returns or how to interpret the response. Given the absence of an output schema, a brief note on the return value would enhance completeness, but the current level is adequate for a straightforward create operation.

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 schema provides descriptions for all parameters, achieving 100% coverage. The description does not add any additional parameter-level information, so it aligns with the baseline score of 3 for high schema coverage.

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 tool's primary action: 'Create a product listing.' It also mentions validation against category spec and return policy, which adds specificity. This distinguishes it from sibling tools like seller_update_listing or seller_list_listings.

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 when to use it (to create a new listing) and gives context on validation steps, but it doesn't explicitly contrast with alternatives like seller_update_listing or services_create_listing. Still, the purpose is clear enough for an agent to infer usage.

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