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

With no annotations, the description carries the full load and does well: it discloses the three status states, the fact that the full kit is returned only once delivered, the $19 one-time Stripe payment path, and that crypto is unsupported. It omits polling cadence and behavior for an unknown/invalid preview_id.

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?

One dense, front-loaded sentence with the trigger condition first and outcomes second. The pricing/payment-channel clause is useful orientation but is the least load-bearing part of the sentence.

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?

There is no output schema, and the description does a reasonable job describing the return shape (status enum plus full kit when delivered). The remaining gap is the undocumented preview_id and polling expectations, which matters for a poll-based tool but does not make the definition unusable.

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 0% for the single preview_id parameter, so the description must compensate. 'After paying' weakly implies preview_id identifies the specific kit purchase being polled, but the parameter is never named or explained, and its format/source is left to inference.

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 verb+resource: it returns a purchase status with the enumerated states (not_on_sale | awaiting_payment | delivered) and the full kit once delivered. That is far more specific than the sibling names suggest, though it never explicitly says how it differs from listing_kit_get or listing_kit_preview.

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?

The phrase 'Poll after paying' gives a clear usage context and implies repeated invocation, which is useful. But it does not say what to do before paying, how often to poll, or why an agent would choose this over the sibling listing_kit_get.

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