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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds one genuine behavioral fact beyond that: WooCommerce must be active, which is a precondition the annotations do not express. It says nothing about pagination or result limits, so it lands at 3.

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 tight sentences with zero filler, front-loaded with the operation and then narrowed by the precondition. It is appropriately sized, though its terseness is also the source of the parameter gaps.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. The remaining hole is input-side: with four undocumented parameters at 0% schema coverage, the agent gets no guidance on paging (page/per_page defaults) or on how site_url selects among connected WordPress sites, which is material for a multi-site connector.

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% across four parameters (page, per_page, search, site_url), and the description compensates for none of them. The fields it enumerates (name, SKU, price, stock) are output attributes, not inputs, so it adds no meaning to page/per_page/search/site_url.

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 states a specific verb (List) and resource (WooCommerce products) and enumerates the returned fields (name, SKU, price, stock, status), so the agent knows exactly what it gets. It is distinguishable from wordpress_woo_orders and wordpress_woo_create_product by resource, but it never names those siblings explicitly, keeping it at a 4 rather than a 5.

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?

Usage is only implied: it applies to a connected WordPress site with WooCommerce active, which is stated as a prerequisite. There is no explicit when-to-use versus the sibling listing tools (orders, posts, plugins) and no exclusions or alternative routing.

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