tpt_list_products

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds a meaningful scope qualifier ('local upload-ready'), but it does not explain what 'upload-ready' means or whether the list reflects some internal saved state. This is adequate but not richly transparent.

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?

The description is one clean, front-loaded sentence with no filler. Every word adds meaning, making it an excellent example of concise tool documentation.

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 a zero-parameter read-only listing tool, the description is largely sufficient. The main missing piece is the exact shape or meaning of the returned 'local upload-ready products', but with no output schema and a simple action, this is a minor gap rather than a critical omission.

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 input schema has zero parameters and the description introduces no ambiguous parameter-like concepts. Since there is nothing to document, the baseline for a zero-parameter tool is appropriate.

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 uses a specific verb ('List') plus a resource ('local upload-ready products'), making the tool's function immediately clear. It does not explicitly contrast with siblings like tpt_get_product or tpt_product_status, but the wording is precise enough to distinguish a collection listing from a single-product or status operation.

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 'local upload-ready products' implies the tool should be used to enumerate products that are ready to be uploaded, which gives some usage context. However, the description provides no explicit guidance on when to choose this tool over sibling tools such as tpt_prepare_product or tpt_product_status.

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