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

Beyond the annotations (readOnly=false, destructive=false, idempotent=false, openWorld=true), the description discloses the material consequences: nothing is published or charged until the claim link is opened and submitted, the automatic check either publishes or holds for review, and Premium returns a Stripe Checkout link paid in the browser. Those are exactly the behavioral facts an agent needs before invoking a write with real-world effects.

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 filler, and the conditional auth mode is front-loaded so the branching is visible immediately. It is dense — the second sentence chains submission, auto-check, and Premium checkout in one breath — which costs a little readability but nothing is redundant.

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 eight-parameter, seven-required creation tool with an output schema already describing returns, the description covers both auth paths, the publish/review branch, the charge deferral, and the claim-link flow. It does not restate return values, which is correct given the output schema, and nothing an agent needs to call it correctly is missing.

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 eight parameters is already documented in the schema, including the plan enum and the pricing_model meaning. The description only reinforces the plan parameter's deferred-charge semantics and adds no field-level guidance beyond that, so the baseline 3 applies.

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 names a specific verb (saves/submits) and resource (a product listing on Neeed Directory) and splits it into two clearly distinct modes: an unauthenticated draft with a claim link, and an authenticated submission. An agent can distinguish it from update_listing or upgrade_listing because the draft/claim-link flow and the publish-or-review check are unique to this tool.

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?

It gives explicit preconditions for each path — 'Without sign-in' versus 'Signed in with permission to edit listings' — so an agent can tell which outcome to expect from the current auth state. It does not explicitly name sibling tools such as upgrade_listing or update_listing as alternatives for existing listings, which keeps it short of a 5.

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