create_listing

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

Annotations only declare destructiveHint=true and a title, so the description does the real work: it discloses that the result is an unpublished draft, the dataset_id return value, and the follow-up publish step needed to go live. It does not cover auth/permission requirements or that draft fields can be amended later, keeping it short of a 5.

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?

Three tight sentences with zero filler; the core action and return value are front-loaded, and the pricing rule and lifecycle follow-ups are each stated once.

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 11-parameter tool with nested objects and no output schema, the description covers the essential what, the return value, the pricing decision, and the lifecycle chain. It omits guidance on auction_config/hybrid pricing and documentation requirements (e.g. source_name before publishing), which a caller would need for non-default listing types.

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 91%, so the baseline is 3, but the description adds genuine cross-parameter meaning: price vs price_cents mutual exclusivity and the default-to-free behavior when both are omitted. It says nothing about auction_config or schema/format options, which remain schema-only.

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?

Specific verb+resource+scope: 'Create a new draft dataset listing on DataBazaar' and it names the return value (dataset_id). The word 'draft' immediately distinguishes it from publish_listing and update_listing, so an agent can place it in the lifecycle without opening a schema.

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?

Explicit sequencing guidance: create, then get_upload_urls to upload files, then publish_listing to go live, plus the rule that omitting both price fields creates a free listing. It lacks an explicit 'when not to use this' exclusion (e.g. vs suggest_listing or update_listing), but the workflow context is clear.

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