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

With no annotations at all, the description carries the full burden and does add genuinely useful behavior: submissions are AI-moderated, links are verified, and the listing does not go live immediately. It omits what the agent needs most for a mutating, payment-adjacent tool — what happens if moderation fails, whether the call is idempotent, what auth is required, and what identifier comes back.

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 tight sentences, front-loaded with the action and immediately followed by the key gating fact. Nothing is wasted, though for a 12-parameter create flow with payment logic the brevity shades into under-specification rather than pure economy.

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?

With no annotations, no output schema, and 12 parameters including a money path, the description should cover auth expectations, what a successful return looks like (listing id or pending status), and failure modes. It covers only the moderation gate, leaving the agent to infer the rest from the schema alone.

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 every one of the 12 parameters (including the sell_here/link_url/price_type interdependency) is already documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline 3 when the schema does the heavy lifting.

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?

"Publish a product or service" gives a specific verb (publish) and resource (listing) that an agent can map cleanly to the create_listing name. It is distinguishable from update_listing and delete_listing by the create framing, but the description never explicitly contrasts itself with those siblings.

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 on when to use this instead of update_listing, no mention of prerequisites (an API key, or a payout wallet before sell_here=true), and no note that list_categories should be consulted first. The only usage signal is the moderation gate, which is a consequence rather than a selection criterion.

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