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

With no annotations, the description carries the full burden and does well: it discloses the pending-review queue outcome, an auth prerequisite plus the sign-in escape hatch, and the important non-obvious side effect that a duplicate URL mutates the existing listing's submitter details rather than creating a new record. It omits what the response looks like beyond the URL.

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?

Four short sentences, front-loaded with the action and then layering outcome, duplicate behavior, and auth. Every sentence carries information; only the auth sentence is slightly self-referential in a way that reads awkwardly against 'requires an authenticated connection'.

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?

The description covers outcome, duplicate handling, and auth, which is most of what an agent needs. But for a tool that claims to submit a product while exposing zero input parameters, the description never explains how the product is actually specified, leaving a real gap in invocation understanding.

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?

The schema has zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description does add that the return value is a URL for finishing/tracking the submission, which is value beyond the empty 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?

Specific verb+resource ('Submit a product to the directory') with the actor scoped ('on behalf of the connected user'). It is clearly distinguishable from get_listing/search_listings, though it doesn't explicitly differentiate itself from the closest sibling, submit_review.

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 a clear condition for calling (submitting a product for the connected user) and a useful invocable fallback ('call this tool to get the sign-in instructions' when unauthenticated). It does not name alternatives or state when not to use it.

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