create_listing

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

Discloses that it creates a draft (not published) and returns listing_id. With no annotations, it carries the burden adequately, though could mention more about side effects or validation.

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?

Two sentences, no waste. Front-loaded with action, then specific instruction and result. Highly efficient.

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?

Covers core purpose and return value but lacks workflow context (draft->publish) and depth on required parameters or behavior, given 14 parameters and no output schema.

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 covers 71% of parameters; description adds value for the 'type' parameter and return value, but does not explain many other parameters beyond schema.

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?

Clearly states 'Create a new draft listing.' distinguishes from siblings like publish_listing and update_listing, and provides a specific use case for digital products.

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?

Gives one conditional usage tip (digital products), but lacks general guidance on when to use this versus other listing creation or modification tools, or prerequisites like taxonomy_id.

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