Lists WooCommerce products created as drafts but not yet published, newest first, so you can review what still needs checking or publishing in wp-admin.
Prodotti creati con crea_prodotto e non ancora pubblicati, piu' recenti prima: promemoria di cosa resta da rivedere su wp-admin.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must carry the behavioral load. It usefully discloses ordering (most recent first) and the draft-only filter, and the read-only nature is implied, but it says nothing about pagination, result limits, or permission requirements.
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?
Two short clauses, front-loaded with the resource definition and filter before the ordering note. No wasted words.
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 an output schema present and zero parameters, return-shape explanation is unnecessary. The description supplies the filter, ordering, and purpose; only edge-case behavior (empty list, volume limits) is unaddressed.
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 tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool 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 resource and scope: draft products created via crea_prodotto that are not yet published, ordered most-recent-first. This clearly separates it from the generic lista_prodotti sibling, though it doesn't explicitly name that sibling as the alternative.
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 'promemoria di cosa resta da rivedere su wp-admin' implies the usage context (review queue), and referencing crea_prodotto hints at provenance, but there is no explicit statement of when to use this over lista_prodotti or lista_stato_seo_prodotti.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.