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

Annotations only declare non-read-only, non-destructive, idempotent; the description adds substantial context beyond them: nothing is published, the draft appears on the Sell tab under 'Not live yet', eBay connection state and connect link are returned, and reconnecting lands the user back on the same item. This is exactly the behavioral detail an agent needs.

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?

Front-loads the actor precondition and the core action, and every clause carries real information. It is dense with parentheticals and slightly long-winded, but no sentence is wasted.

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 output schema, the description still explains what is returned (review link, eBay connected flag, connect link), the side effects (draft inventory item, no publication), and the user-visible result location. 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 coverage is 100%, so the schema already documents all four parameters, and the description largely restates them (title, list price defaulting to market price, condition). It adds no syntax or format detail beyond the schema, so the baseline of 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?

States a specific transformation: a photo scan from price_item becomes an inventory item with a draft eBay listing, returning a review link plus connection status. It also disambiguates from the sibling price_item (its input source) and clarifies that despite the name, it never actually publishes.

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?

Specifies the precondition (signed-in user with a price_item scan) and the downstream step (user reviews and publishes in the app). It does not name a specific alternative tool to use instead, but the when-to-use context and the explicit boundary against publishing are clear.

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