create_listing

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a marketplace seller listing' implies a mutating operation but does not reveal side effects, authentication needs, draft vs. public status implications, or what the response will contain. This is a significant gap for a mutation tool with zero annotation coverage.

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, front-loaded sentence with no filler words. It is concise and easy to parse, though its brevity leaves important details unaddressed in other dimensions.

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?

This is a 10-parameter, 3-required-parameter mutation tool with no annotations, no output schema, and zero schema description coverage. A one-sentence description is far too thin to enable correct invocation, especially with lots of sibling tools and optional fields like status, allowOffers, and sleeveCondition.

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 0%, and the description adds no meaning to any of the 10 parameters. The input schema provides only names, types, and constraints, so the agent receives no assistance understanding what releaseId, condition, price, status, or other fields represent in context.

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 states a specific action ('Create') and a specific resource ('marketplace seller listing'), clearly distinguishing it from sibling tools like get_listing, edit_listing, and add_to_collection. The phrase 'marketplace seller' removes ambiguity about which kind of listing is being created.

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?

There is no guidance about when to choose this tool over alternatives such as edit_listing or delete_listing, nor any mention of prerequisites like having inventory or a release to list. The description only states the action, leaving the usage context entirely to inference.

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