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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the authentication model (local WordPress auth, no WooCommerce REST API keys), which is not in the annotations. However, with no output schema present, it says nothing about what the returned product object contains or how missing IDs are handled, leaving that behavioral gap unaddressed.

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 sentences with the core action stated first and the operational context second; nothing is padded. The 'mirrors woocommerce-mcp-server method get_product' clause is arguably meta-information, but it is brief and signals output parity with a known server.

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 simple two-parameter read tool with full schema coverage and clear annotations, the essentials are covered. The notable omission is any description of the return payload or error behavior (e.g., nonexistent product ID), which matters since no output schema exists.

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 coverage is 100%, and the schema itself explains that site_id comes from list_sites and is not a URL or post ID, and that productId is the product ID. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 gives a specific verb and resource: 'Gets one WooCommerce product by ID.' An agent can immediately tell this is a single-item fetch rather than a list, and the mention of mirroring `get_product` in woocommerce-mcp-server reinforces the shape of the result. It does not explicitly contrast with siblings like wc_get_product_variation or wc_get_product_meta, but 'product by ID' is specific enough to distinguish the entity.

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 description implies usage (fetch a single product when you have its ID) and adds a useful prerequisite about authentication, but it never states when to prefer this over siblings such as wc_get_product_variation or when not to use it. The site_id schema note ('Call list_sites first') supplies some procedural guidance, though that lives in the schema rather than the description.

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