tpt_prepare_product

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

Annotations already indicate mutating and destructive behavior, so the description doesn't need to restate that. It adds useful behavioral context by clarifying that submission is not performed and that upload completion should be inspected afterward.

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?

Three concise sentences with no filler. The main actions lead, the non-submission clarification follows, and the post-step is given last. Each sentence earns its place.

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 tool likely has a multi-step workflow with uploads, but the description omits what 'id' means, where the listing.json and files come from, prerequisites such as login, and what the caller should expect in return. Without an output schema, more guidance is needed.

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 0% description coverage for the single 'id' parameter, and the description never mentions 'id' or explains what it refers to. An agent cannot determine whether 'id' identifies the product, listing, or something else.

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 specific actions (validate, fill, upload) and concrete resources (listing.json, seller fields, ZIP, PDF preview, four images). It also distinguishes itself from sibling submission workflow by explicitly saying 'Does not submit.'

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 conveys when to use the tool: once the listing.json is complete and before submission. The explicit 'Does not submit' provides a clear exclusion, though it doesn't name sibling alternatives such as tpt_submit_product or tpt_verify_saved_product.

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